yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 Themes and Apps] moose m79:
Huawei E372 PPP widget says no modem

My rooted Rikomagic 802 mkiv 4.2.2 stick does not recognize my Huawei E372 modem.

I installed supersu, busybox pro, PPP widget 2

It asks twice about the USB device but PPP widget says no modem. Status bar shows triangle. No modem light show please help
[Galaxy Tab 2 Themes and Apps] JFDee:
Did you read the description of PPP Widget at Google Play?

It says you need a powered USB hub. Most tablets do not provide enough power on their OTG ports. Modems need the full load.

The "triangle" - if you open your notifications - will likely say something about 'current'.

Also, the original post is WRONG stating that PPP Widget "works for all external modems". Again, read the Google Play description carefully.

JFDee, PPP Widget 1/2 developer
[Galaxy Tab 2 Themes and Apps] valimaties:
Here is my video, connecting this modem to an Android device (Car Navigation by Joying)

h t t p s :// www .youtube. com/watch?v=DQRvgIhW1D8

It is made in romanian language, so I made an english subtitle. Please activate subtitles :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ilichbustamante:
Hey guys, i have a problem when i connecting to a one server in the OpenVPN Settings. When says: Get config, appearing a problem: Linux ifconfig failed: could not execute external program and im dying with this problem, i cant solve this, PLEASE HELP ME

I have Sony Ericsson Live With Walkman (wt19)

Rom: Serenity Ultimate Edition V 3.0

Kernel: 2.6.32.9-perf

PLEASEEE !
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ilichbustamante:
Any ? Any cant help me ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ilichbustamante:
Help me !
[Member-Found Deals] m4f1050:
http://www.ebay.com/itm/120983253654

I own one and they work great. Use it as a Netflix player (using HDMI cable), both micro USB are OTG, only down is power, it's small 2.5" (or mm?) plug but they sell car adapters and I made a usb cable (charges with USB current well, lasts longer connected) and the speakers. I bought Aluratek Bump for it. Runs ICS and it also has Ethernet drivers for cheap 9700 chipset usb to ethernet adapter (like a buck or two) 3.5" audio is excellent. It's capacitive and it also has microSD card reader, hardware power, vol -, vol +, reset and back button, it has both front and rear 2mp camera (they aren't the greatest but they work) 16 gb also.

Chipset is RK3066

Sorry for poor image, it was dark
[Galaxy S II Q&A, Help & Troubleshooting] Fulgore.:
Hello, I got a problem that started few months ago, almost every time I restart my phone (usually to apply AdFree / AdAway updates) when It's in the 50-60% range it drops to around 10-20%.

I switched roms, kernels but nothing seems to change.

I have no idea what triggers it but obviously its really annoying.

Need some advice please.
[Galaxy S II Q&A, Help & Troubleshooting] Paulius7:
It's insane faulty chip it does for everyone..

When device is hot it drop battery...

But sometimes it drops but device it's not hot...

But sometimes it form 10% goes to 50%

Merry christmas and Happy new year

Paulius
[HTC One X+] Pion33r:
Hello Developers,

as I'm a huge Fan of all your work I'd first of all thank you for enriching my digital life so much with your hard work.

Now to the subject: I can't understand that HTC resigned in Sense 4+ from the feature of the Quick Settings :eek:

A college of mine has the One X and another one has the One S and they are all the time making fun of me for missing that feature.

Do you think it will be possible in the near future to add this feature or import it from an One x rom or make a Sense 4 rom (without +).

Thank you in advance for your replies.
[HTC One X+] -=knop=-:
+1
[HTC One X+] nchantmnt:
how about just adding quick settings to the notification pulldown? i didn't take a too sharp look at the roms availlable, so i don't know if any other but cyanogenmod does have this feature yet. but you could on any rom always install the app widgetsoid and add the quick settings panel yourself.

here's a link: https://play.google.com/store/apps/details?id=com.jim2

it's free, customizable and easy to set up. just take a look at the screenshots and you know what i mean ;)

btw: i guess that they dumped these settings because they will (hopefully soon) give us android 4.2 for our one x+ which will already feature a quick settings tab in the notification pulldown. i think it wouldn't make any sense ( pun-alert) to build in a feature which will surely be dumped on the next major os upgrade which is sure to be delivered in near future.
[HTC One X+] Pion33r:
Hey,

i have tried several of these notification apps, but it' snot the same... Long press doesn't bring you directly to the settings, no direct brigness adjustment... etc.

I\m just a little dissapointed as i had been faithfull to HTC now with the third android (Desire - Sensation - One X+) and i never experienced a fall back in the development :( Quick settings had been already developed by Leedroid at Froyo times and even Miui is famous for this feature. Gues i just bought a too new phone that doesn't yet have real modified rom's available.

Additional: in the wigdet add that you recommend the flashlight doesn't work ;)
[HTC One X+] baste07:
l Use notification toggles
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
Can anybody help me? I have been having this problem with my NOOKcolor i flashed cm7.2 on it and once i am on the home screen my NOOKcolor just shuts down and reboot itself again. :confused::confused::confused:
[Nook Color Q&A, Help & Troubleshooting] japaneezy:
I would wipe and re-flash. Something obviously didn't go right :-\
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
If wiping and reflashing does not help, go to my nook color tips thread and look at item A8, bootloops.
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
Can you post the link here? Im new to xda, Sorry for that.
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
I also noticed that after multiple rebooting the NOOKcolor would restart reboot on it own.
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
I had tried wiping and re flashing its perfectly fine now but just right after a few reboots I got the same problem again the NOOKcolor reboots itself again this is getting frustrating but thanks anyway for your solution guys and I hope you guys can help me solve this problem thanks in advance and thanks for reading this hope you have a nice day.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
The link is in my signature. But you are running the xda app and can't see it. See here.

http://xdaforums.com/showthread.php?p=25354258
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
Thanks for putting the link here you are really helpful I would go and check the article now thank you very much.
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
Which cwm file should I download and does doing the things you have listed in A8 solve my problem?
[Nook Color Q&A, Help & Troubleshooting] DizzyDen:
Are you selecting reboot from the power menu? If you are... try powering off... waiting a minute or so and turning it back on... see if that don't fix the reboot issue.
[Nook Color Q&A, Help & Troubleshooting] INEEDHELPPLSHELP:
Thanks. I would try that when i get the rebooting problem again but i wish hopefully not.
[Desire Q&A, Help & Troubleshooting] prabs4sure:
The camera was fine when i rooted and flashed CM7 on my htc desire in October, 2012. Later when I flashed Runnymede with sense, the camera stopped working. After that I tried several ROMS including the earlier CM7 but the camera failed to start. I even tried by installing other camera apps from the market but in vain. PLEASE HELP. Thanks in advance.

To make it further clear- I have formatted the total sd card and done factory reset before every rom installation.
[Desire Q&A, Help & Troubleshooting] frosty68:
Could it be hardware? There's a thread here somewhere about the ribbon cable becoming dislodged and how to fix
[Desire Q&A, Help & Troubleshooting] prabs4sure:
Thanks for ur reply. I will try finding the thread. In case u find it please send the link. Thanks in advance.
[Desire Q&A, Help & Troubleshooting] zeka16:
I have the exact same problem!

Everything was fine until I tried Runnymede AIO.

Now the camera doesn't work on leedroid or cm7 and I can't install miui without getting reboots.

Any suggestions?
[Desire Q&A, Help & Troubleshooting] KirovAir:
What kernel are you on right now?
[Desire Q&A, Help & Troubleshooting] zeka16:
I'm currently on CM7 and under kernel version I see:

2.6.37.6-cyanogenmod-g2a32a61
[Motorola Droid RAZR] TreZoRA:
hello guys, i'm very nervous now

my device is rooted and from google play i downloaded this app : Beats Audio™ Installer ★ root

after installing it , device asked to restart and after that , when turning on it is stucked on this area

cache.itsagadget.com/uploads/2011/10/Motorola-Droid-Razr.jpg

so when i connected it with usb to computer, copmputer sees it

please help me, i bought it yesterday :(
[Motorola Droid RAZR] anooparavindp:
Try a cache wipe

Hi mate,

Why don't you try a cache and Dalvik cache wipe ?
[HTC One S] armorized:
I had a T-Mobile G2 from launch and just about killed it. I had to get a phone out of necessity and got the Samsung Galaxy nexus as a temporary replacement.

I really do not like this phone lol. I miss sense and was holding out in hopes of T-Mo getting the HTC one x+ but that didn't happen.

So I pose the question of should I get the T-Mobile one s or get an unlocked one from expansys or just wait it out. I live in an area that was refarmed to 1900mhz so I could get the one x+ or even a droid DNA if I manage to get an unlocked one.

But with those last two choices I'd have to be able to live with 3g instead of HSDPA.

I think I could probably get a free upgrade since I bought this phone unlocked from Google but I can't make up my mind. I also can't stand aosp anymore though. I really want sense lol.

Thanks in advance.
[Nexus 7 Original Development] osm0sis:
Update Instructions

Updating When A New Bootloader Is Released

Once built for your device, the above script will work as long as the bootloader remains at v4.23 (as per the naming). The way I've scripted it, for safety it shouldn't work on any other bootloader version or on anyone else's device, but I'd still advise against trying. Since the encrypted data also changes based on the version of the bootloader, if/when you update the bootloader you MUST also get NEW dumps of the mmcblk0boot0 partition both unlocked and locked.

BEFORE you update your bootloader, if your device is locked, start by using the BootUnlocker Script zip you previously created to unlock.

Update your bootloader to the new version (usually done via OTA or fastboot flash of a Factory Image).

Follow the steps in the 2nd post again to update your zip, replacing the .img files with the new dumps, and altering the update-script with the new corresponding sha1sums.

Change the version number in the updater-script warning on line 6 and the version number check on lines 22+23 to that of the new bootloader, and be sure you have renamed the zip with the new version number as well to keep things straight.

"adb shell" in while booted to custom recovery and run the following, copy+paste the bytesize and sha1sum for the next step.

dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/tmp/USP.img
sha1sum /tmp/USP.img
rm /tmp/USP.img

Enter the new bootloader's bytesize and sha1sum into the bootloader version check on line 21, in the following format USP:<bytesize>:<bootloader sha1sum>, eg. for v4.23 it is

USP:10485760:8c206a1a87599f532ce68675536f0b1546900d7a

Enjoy!

Questions, comments and feedback welcome.

Thanks to segv11 and efrant for all the fun in the GN BootUnlocker App thread, scary alien for the help with the bootloader check assert syntax in his OTA Verifier App thread, and thanks to trevd for the update-binary info/help in the GN EDIFY Scripting thread. Also a special thank you to Mach3.2, scary alien, partha and drose6102 for submitting dumps so all this could be figured out, and for basically being the Beta/RC testers for this script. Cheers!
[Nexus 7 Original Development] Misledz:
You finally got it working! I ought to try this, of course after wrestling with the grizzly dad of mine. Awesome job there Chris!
[Nexus 7 Original Development] osm0sis:
Haha yup. I've had it working for awhile now, it was just a matter of writing up this monster guide. ;) Thanks Fitz. Good luck with that wrestling. :p
[Nexus 7 Original Development] phonic:
Very cool, and very nice work.
[Nexus 7 Original Development] lilstevie:
The encryption does not change, that is static for the life of the device, what changes is the data stored. Also boot0/1 are technically not partitions and are more analogous to mmcblk0 than mmcblk0px there are 3 partitions that start within this range, BCT, PT and the start of the bootloader. BCT takes up the entire boot0 and part of boot1.

The reason you cannot just flash back your backup copy is a hash of the bootloader is stored in the bct for verification and integrity checking purposes[1]. This changes the end result because all SBK encrypted data is done in AES-128-CBC meaning the previous blocks cipher text is the next blocks IV.

Because of this you should also be careful of any number of other conditions that cause writing to the BCT as they have the potential to cause the decryption to fail on the rest of the BCT which is in mmcblk0boot1. While this may not (and at this point should not) cause bricking, changes made by google in the future may alter this outcome.

[1] The hash stored in BCT not matching the bootloader hash causes the device to fall back into APX mode.
[Nexus 7 Original Development] osm0sis:
Hey great to finally get some more information about the encryption used and the contents of boot0-1. Very interesting stuff. :) How did you determine this? We couldn't find much documentation on the matter. Any ideas on how to decrypt it would also be greatly appreciated, since that might allow segv11 to still be able to include it in the BootUnlocker app.

So far the only time we've seen the md5hash of the boot0 block change on a particular device is with a bootloader version change, after which it continues to remain consistent depending on lockstate. I was merely guessing that was part of the encryption process but the data changing would of course also make perfect sense, so thank you for that information. What doesn't change when unlocking/locking the bootloader is boot1, so flipping between the two states for boot0 will still keep decryption of boot1 intact.

I definitely understand your concerns that it is a dangerous business writing to these blocks, and I agree, but as you've seen I haven't taken this lightly in either my posts or my script; the script has safeties built in to make sure it only writes to boot0 when it meets one of the two known states for that person's device (locked or unlocked). If somehow the boot0 did change randomly in the future without a bootloader update then the script wouldn't run, it would abort, questioning whether this was the intended device or not since it couldn't determine the lockstate from the stored sha1sums. :good:
[Nexus 7 Original Development] lilstevie:
it is off the shelf tegra security. As I said at this time changes shouldn't echo all the way through, but the BCT partition is usually ~3MB but only uses a fraction of that.

Decryption and Encryption of the data is not something easily available, it entirely defeats the purpose of it if you can do it yourself.
[Nexus 7 Original Development] osm0sis:
Haha yeah of course it defeats the purpose, but in a way so does unlocking the bootloader with root. ;)

Either way, thanks for the help and your Tegra knowledge. :)
[Nexus 7 Original Development] deepdespair:
Works perfect

Thanks a ton osm0sis. Just tested and it's flawless. Finally got rid of that unsightly unlock icon when you first boot and I still have full functionality. Locks and unlocks in an instant with the edited .zip file. Great work! :highfive:
[Nexus 7 Original Development] slyb5:
I am very interested in unlocking the bootloader without rooting or fastboot oem unlock my device. I'd love to find that key and be able to write an encrypted bootloader via JTAG access for example (I guess can't do otherwise to write an encrypted image as the encryption is probably done by the bootloader while uploading an image through fastboot am I right?)

I foresee 2 possibilities, but might be very wrong: 1) key hardcoded (in the BIOS for ex), I am trying to see if I can JTAG access the processor next week (theoretically frist, as my N7 arrives after 2 weeks)

2) the key is computed based on the device serial number (which I think might very well be the case) at startup (I'd guess a logical operation like an XOR on the serial maybe with a master key hardcoded or just a crypto op on the serial) in this case it might not be required to search for it in a memory dump but aska crypto guy see if with the knowledge of cyphered data, the algorithm and the serial, a key could be diversified...

If some of you guys are interested to work on that...we could open a new thread?

Meanwhile any of you know where I can get more info on the memory map of the flash?
[Nexus 7 Original Development] osm0sis:
My guess was that it was device serial number based as well. If you want to work on decrypting it, you could probably take it back to the main BootUnlocker App Dev thread: http://xdaforums.com/showthread.php?t=1731993, since if you ever got it working it could likely be included in the app again. :)

No idea on the memory map unfortunately.
[Nexus 7 Original Development] osm0sis:
Just a reminder to everyone to unlock

before

you flash the OTA. Instructions for updating the script for new bootloader versions are in the 3rd post of this thread.

Happy OTA Day! :)
[Nexus 7 Original Development] sebarkh:
What is strange USP.img sha1 did not change. It still is 8c206a1a87599f532ce68675536f0b1546900d7a

???

---------- Post added at 06:07 PM ---------- Previous post was at 05:58 PM ----------

Anyway....working ok with 4.2.2 after updating with post 2 instructions.
[Nexus 7 Original Development] osm0sis:
You're right, interesting! My guess, based on what lilstevie said, is that when the OTA writes the new bootloader to /USP it actually writes it to multiple contiguous partitions starting with USP, including the mmcblk0boot ones we dump. So whatever changed in the bootloader didn't alter the actual USP part this time, and that's why it checksums the same. The mmcblk0boot blocks do change, so the method in post 3 should still be followed.
[Nexus 7 Original Development] deepdespair:
Just updated to 4.18 and followed the instructions (minus the USP section in post 3) and all is working as expected. Thanks again!
[Nexus 7 Original Development] osm0sis:
Just noticed that having the mount /system in an assert will actually fail the assert if the system is already mounted. Not really a big deal, just means /system can't already be mounted when you go to run the BootUnlocker script or it won't make it past the device check. I haven't decided whether it matters enough to upload a new version of the script zip or not, since it's easy enough to go unmount /system before running it.

Also easy enough to fix it yourselves if you like:

assert(mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system"),
getprop("ro.product.device") == "grouper" ||
getprop("ro.build.product") == "grouper");

should instead be:

mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
assert(getprop("ro.product.device") == "grouper" ||
getprop("ro.build.product") == "grouper");

Anyway, thought I'd give everyone the heads up even though nobody's apparently run into it or brought it to my attention before. ;):good:
[Nexus 7 Original Development] pof:
Thanks for your tips! As I prefer to use the stock recovery I made a script to use your solution from the device itself, placing the partition backups in /system/usr/bootunlock. Here it is in case anyone else finds it useful:

#!/system/bin/sh

case $1 in
"lock")
echo "[x] Locking bootloader..."
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/system/usr/bootunlock/locked-mmcblk0boot0.img of=/dev/block/mmcblk0boot0
echo 1 > /sys/block/mmcblk0boot0/force_ro
echo "[x] Bootloader locked!"

;;
"unlock")
echo "[x] Unlocking bootloader..."
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/system/usr/bootunlock/unlocked-mmcblk0boot0.img of=/dev/block/mmcblk0boot0
echo 1 > /sys/block/mmcblk0boot0/force_ro
echo "[x] Bootloader unlocked!"
;;
*)
echo "Usage: $0 <lock|unlock>"
exit 1
;;
esac
[Nexus 7 Original Development] DIXES:
Does it still work on the latest bootloader of Androud 4.3?

I just need to change the value in script and replace img files?

Thanks.
[Nexus 7 Original Development] osm0sis:
Follow the instructions for updating bootloader in the 3rd post. It should work regardless of bootloader version since I doubt their implementation is going to change now. :good: :)
[Nexus 7 Original Development] Deeco7:
Was hoping to unlock my bootloader without data wipe with the bootloader being locked, from reading your op...looks like it isn't possible, nonetheless great script.
[Nexus 7 Original Development] osm0sis:
Nah unfortunately not possible because of the encryption. Thank nVidia.
[Nexus 7 Original Development] osm0sis:
Updated the N7 BootUnlocker base script zip in post 2:

v4.23:

- Fix the mount issue of the previous version.

- Display current device name and bootloader version to help identify user-errors.

- Check for the actual bootloader version number from getprop, as well as still checking checksum (which doesn't seem to change often).

The last item in particular should make this a bit safer, and while the checksum doesn't change often/ever, I left that check in place so that if the checksum/data ever did get altered without the number changing, that's still a red flag and will stop the process.

The instructions have also been updated to reflect these changes and new line positions. :good:
[Nexus 7 Original Development] igerup:
Wow, this is cool and awesome. The annoying loss of data (there's always backups, but still) when unlocking via fastboot is no more. Thank you :)
[Nexus 7 Original Development] wkwkwk:
Hi,

Is it possible to run the unlock/lock script (basically the dd command) out of android itself rather than from recovery?

The whole purpose from my point of view is to put a stock recovery and lock the bootloader, otherwise with a custom recovery (twrp) it has root access to the device so there's no point in locking the bootloader.

If need be, from android os I can then unlock the bootloader and flash TWRP and when I'm done, flash the stock recovery and lock the bootloader.

Thanks.
[Nexus 7 Original Development] osm0sis:
Sure if you retain root. Make a directory, /data/lockstates/ and put your dumps in there, then using the shell commands from the EDIFY script you could flash them as you like; or even a shell script if you prefer. Good idea actually, I'll work on it tomorrow. :)
[Nexus 7 Original Development] wkwkwk:
Excellent, thank you.

Tested and it works, I just wanted to double check before doing anything.

There's actually a script in page 2. The syntax seems to have an issue with CM10.2 but I ran manually dd and it works to lock/unlock.

Good stuff, thanks for all your work.

By the way, out of curiosity, if you mess up the bootloader somehow, is there a 'download mode' where you can reflash it? Something similar to omapflash for TI?