Just recently purchased Bungbungame MiSS (Tegra 3, nice screen) etc. Have unlock bootloader, but cannot seem to get root access. su is not in system/bin or system/xbin directories and when I attempt to use su in SSH I get a permission denied. Cannot mount as "read-only file system".
Thanks in advance for any help
DT
I have the MiSS as well, just started trying to look at how to root it. Appreciate any info you find.
BUMP...
Anyone figure out how to root one of these Bungbungame MI100 tablets yet? Just got mine today. Pretty sweet for the price, just need to get ROOT!
bumpbumpbumpbump!!!
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
[/COLOR]Enter Recovery Menu
Hold down power and volume up at the same time, then as soon as the screen flashes on, let go of the power button and you should see something like this in the left top corner OTA....... start pressing the volume down button and volume up simotanously about 4-5 times then it will enter recovery menu. Next i will try to push the crystal root method through recovery in adb push update to see if that roots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ok that didnt go well i ended up getting a android with an exclamation mark
but also wanted to note that im on my windows 7 machine and i already had the manufacture drivers installed working in regular adb mode....and when i was in the cmd and my device was in adb sideload mode it wasnt being recognized, so i looked in my device manager and i had a exclamation by my miss device. The tablet usually works perfectly fine when im booted up and in adb cmd no problems with the drivers at all, im able to log cat and read my device HOWEVER when im in adb and my tablet is in recovery adb sideload all of a sudden the drivers werent acting right and i couldnt communicate with adb cmd and my device.......so what i did was googled apx no driver found because the message coming up when the drivers were trying to be detected was just that "apx no driver found" so i have this link here http://forum.xda-developers.com/showthread.php?t=1998650 and downloaded it and then went to my devices and updated the drivers under the MiSs driver and after installing it made my driver name into google android driver...then i went back to cmd adb and i was able to sideload the update file to my device..... The update zip installation was aborted but at least i know how to sideload in adb now with the correct driver needed. When i rebooted my device into regualr mode and plugged it into my pc my device manager reads miSS still...and when i jump back into sideloading through recovery menu my manager device puts me back under google driver blablablabla so i guess you guys will probably need this driver too if you want to do some work....its made for Universal TEGRA devices.
I also used these commands to sideload and placed the update.zip where i was pointing to the adb.exe heres the link
http://www.droid-life.com/2013/02/12/guide-how-to-use-adb-sideload-to-update-a-nexus-without-root-or-custom-recovery/
dtippey said:
Just recently purchased Bungbungame MiSS (Tegra 3, nice screen) etc. Have unlock bootloader, but cannot seem to get root access. su is not in system/bin or system/xbin directories and when I attempt to use su in SSH I get a permission denied. Cannot mount as "read-only file system".
Thanks in advance for any help
DT
Click to expand...
Click to collapse
how did you unlock the bootloaders? Did you do this manually with Linux or did you use a program?
BungBungame Has a safemode
Im not to sure what i can do in safe mode with this True Android 4.1.1 bungbungame device but i managed to get into safemode heres what i did..
1) download this root method (RootDebugfs) http://forum.xda-developers.com/showthread.php?t=1706588 and select root (your device will reboot, and freeze at bungbungame logo)
2)Hold both volume up and volume down then release volumes and click them simutanasouly now your device is in safe mode.
here is a picture of safe mode..
BungBungame bootloader menu
When i was connected to adb i entered command "adb reboot bootloader" and i got this menu...also instead of power button being the selection button in the menu the select button is volume up and volume down cycles through the selections power button does nothing.
here is a picture of the menu
unlock MiSS bootloader
No4g4Me said:
how did you unlock the bootloaders? Did you do this manually with Linux or did you use a program?
Click to expand...
Click to collapse
think this link worked - just a variation
at addictivetips.com
look for
what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide
DT
dtippey said:
think this link worked - just a variation
at addictivetips.com
look for
what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide
DT
Click to expand...
Click to collapse
yup that worked thanks i did
STEPS TO UNLOCK BOOTLOADER:
1)adb devices (Type this in ADB, device read)
2)adb reboot bootloader (Type this in ADB)
3)fastboot oem unlock (Type this in ADB)
4)select unlock it (bootloader unlocked sucessfully)
5)reboot device (all user data gets wiped)
note**i had to boot into recovery mode after unlocking bootloader and wipe data/cache (because it frozed)
Yea unlocked bootloader thanks again. Have you tried motochopper root method after unlocking bootloader?
im going to try it now, before it wouldn't
ROOTED SUCCESS!!!!
1)Download Motochopper (http://forum.xda-developers.com/showthread.php?p=40747604)
2)Extract Double click RUN.bat
3)Rooted
YESSSSSSSSSSSSSSSSIR
No4g4Me said:
yup that worked thanks i did
STEPS TO UNLOCK BOOTLOADER:
1)adb devices (Type this in ADB, device read)
2)adb reboot bootloader (Type this in ADB)
3)fastboot oem unlock (Type this in ADB)
4)select unlock it (bootloader unlocked sucessfully)
5)reboot device (all user data gets wiped)
note**i had to boot into recovery mode after unlocking bootloader and wipe data/cache (because it frozed)
Yea unlocked bootloader thanks again. Have you tried motochopper root method after unlocking bootloader?
im going to try it now, before it wouldn't
ROOTED SUCCESS!!!!
1)Download Motochopper (http://forum.xda-developers.com/showthread.php?p=40747604)
2)Extract Double click RUN.bat
3)Rooted
YESSSSSSSSSSSSSSSSIR
Click to expand...
Click to collapse
AWESOME!!! That root method worked for me as well. Thanks for the efforts!!! Now, does anyone think there is there a custom recovery that would work with this?
j36047 said:
AWESOME!!! That root method worked for me as well. Thanks for the efforts!!! Now, does anyone think there is there a custom recovery that would work with this?
Click to expand...
Click to collapse
i think the asus tf201 has the same pit tables so i was going to try and use their recovery from rom manager but im afraid of brick cause its the recovery so instead im going to dump this command in
adb shell....
su......
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
The reason why i say it might work is becuase when my evo shift 4g didnt have a custom recovery the forums said just to use the evo 4g from rom manager. So i did and i was able to flash install and back up successfully. So im tempted to just flash the asus tf201 thing is theres no coming back if the device wont boot recovery like the evo shift 4g had a .exe flash program for recovering to stock in emergencies unlike this bungbung
since my mods and tweaks applied I have amazing performance and battery life I've been using it for about 9hrs straight.I'll post a battery log later.didn't have time for this round which is only the first since the first rooted charge, battery calberation, also use deep sleep battery, and greenify
No4g4Me said:
i think the asus tf201 has the same pit tables so i was going to try and use their recovery from rom manager but im afraid of brick cause its the recovery so instead im going to dump this command in
adb shell....
su......
dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
The reason why i say it might work is becuase when my evo shift 4g didnt have a custom recovery the forums said just to use the evo 4g from rom manager. So i did and i was able to flash install and back up successfully. So im tempted to just flash the asus tf201 thing is theres no coming back if the device wont boot recovery like the evo shift 4g had a .exe flash program for recovering to stock in emergencies unlike this bungbung
Click to expand...
Click to collapse
Yea, I noticed that Rom Manager seems to think this is a tf201 and I was very tempted to try flashing the recovery for it but seriously don't want to wind up with an expensive brick.
j36047 said:
Yea, I noticed that Rom Manager seems to think this is a tf201 and I was very tempted to try flashing the recovery for it but seriously don't want to wind up with an expensive brick.
Click to expand...
Click to collapse
yea your right brick it will be, its actually a miss evaluation on my part the exact brother for this devices processor is the T30 Tablet
Motochopper works! What apps/ mods do you recommended.
No4g4Me said:
yea your right brick it will be, its actually a miss evaluation on my part the exact brother for this devices processor is the T30 Tablet
Click to expand...
Click to collapse
Motochopper works! What apps/ mods do you recommended. Would really like to extend battery life.
Thanks
dtippey said:
Motochopper works! What apps/ mods do you recommended. Would really like to extend battery life.
Thanks
Click to expand...
Click to collapse
Add busybox latest version.Inside romtoolbox the functions that worked are, boot animation, and font changer works, xposed app and xposed install (change the launcher app to DPI 190, Fullscreen and you get a nice size icon going on + put always potrait mode orientation, ill post a screen for that.) Pimp my Rom app use universial Init.d support to activate that, add block and system tweaks for network, VM Heap size, ect....just dont mess with the kernel or cpu because that will lock up your device then you have to reboot then the setting dont stick and also dont apply any flashable mods or tweaks because you dont have a custom recovery yet. The apps to save battery life are DS Battery Saver and Greenify.I got my device up to 4400 one time. Custom kernel would be cool clock it to 1.6 vroooom
Ok, so anyone else's GPS failing to lock after rooting? It sees plenty of satellites, but the notification icon never blinks as if it's trying to lock and no love actually locking on.
Sent from my MiSS using xda app-developers app
j36047 said:
Ok, so anyone else's GPS failing to lock after rooting? It sees plenty of satellites, but the notification icon never blinks as if it's trying to lock and no love actually locking on.
Sent from my MiSS using xda app-developers app
Click to expand...
Click to collapse
it didn't happen to me but I used pimp my ROM app to lock onto my GPS its a mod with in the app. try it out. I did have a few apps force close on me since I rooted they don't want to launch they just kick me out without any error message. but those apps are like a few games I never play anyway.
Related
Hi
I'm trying to change my boot screen to a loading semi circle. I cannot remove bootanimation.zip from /system/media
when I cd to /sys.media and type "rm bootanimation.zip" it asks me with a ?
If I type Y and press enter it says cannot remove "bootanimation.zip":read only file.
what can I do to get rid of the stock skateboard bootscreen?
PS Before typing in any adb cmd's I am typing "su"
First trying doing:
adb remount
Then try your rm command.If the rm command does not work after that, you could try:
adb push bootanimation.zip /system/media/bootanimation.zip
adb reboot
If neither of those work, push it to /data/local. On KaosFroyo, I use this method.:
adb push bootanimation.zip /data/local/bootanimation.zip
adb reboot
synesthete said:
First trying doing:
adb remount
Then try your rm command.If the rm command does not work after that, you could try:
adb push bootanimation.zip /system/media/bootanimation.zip
adb reboot
If neither of those work, push it to /data/local. On KaosFroyo, I use this method.:
adb push bootanimation.zip /data/local
adb reboot
Click to expand...
Click to collapse
I would just adb push to /data/local. It should read from their first.
adb is just over some peoples heads, flashing a zip is easier.
he got his bootani on his phone using my flashable zip from the red cyanogen, he PM'd me
I love how supplying 1 thing to the community can have different uses, that's cool!
Ya that script is awesome. Though this post is about trying to get rid of the 3 skateboard dudes. Unless I'm mis understanding that boot screen and boot animation are the same thing?
Sent from my nonsensikal froyo using XDA App
shatterpoints said:
Ya that script is awesome. Though this post is about trying to get rid of the 3 skateboard dudes. Unless I'm mis understanding that boot screen and boot animation are the same thing?
Sent from my nonsensikal froyo using XDA App
Click to expand...
Click to collapse
Those are there to stay
Poopy. Oh well. Thanks again for the help
Sent from my nonsensikal froyo using XDA App
shatterpoints said:
Hi
I'm trying to change my boot screen to a loading semi circle. I cannot remove bootanimation.zip from /system/media
when I cd to /sys.media and type "rm bootanimation.zip" it asks me with a ?
If I type Y and press enter it says cannot remove "bootanimation.zip":read only file.
what can I do to get rid of the stock skateboard bootscreen?
PS Before typing in any adb cmd's I am typing "su"
Click to expand...
Click to collapse
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
goldenstorm said:
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
Click to expand...
Click to collapse
but the little skateboard droids did nothing to you!!
Two words....root explorer.
Sent from my Droid Eris using XDA App
goldenstorm said:
You can use this to get replace the skateboarding droids -
It works beautifully with Eris, provided you follow directions
Here is the bootscreen I was using on my Eris before getting Fascinate.
I'm having a hard time with this. My eris is already rooted, I cannot flash to the splash1 partition, I only just get an "error cannot load <my file name>" in fast boot. I don't see any clear instructions to flash a different fastboot without re- rooting my phone?
*edit* I got it to want to flash accept now it says "FAILED <remote: not allow>"
*edit2* also I cannot get the s-off bootloader the only place it was available now says its not due to inactivity
Click to expand...
Click to collapse
Ok, now I'm confused. Are you trying to change the boot animation or the boot image? The boot animation is simple to change. Copy new bootanimation.zip to your sd card. Download root explorer, open it and select R/W . Navigate to the sd card and copy the new boot animation. Navigate to system/media and paste. It must be named bootanimation.zip.
If you want to change the boot image (first image you see at boot) that's a completely different process. Go here http://forum.xda-developers.com/archive/index.php/t-654042.html for a how to. I had a little trouble with this at first but got it to work. Scroll down and see my comment for a how to that worked for me.
Good luck!
Sent from my Droid Eris using XDA App
joshw0000 said:
Ok, now I'm confused. Are you trying to change the boot animation or the boot image? The boot animation is simple to change. Copy new bootanimation.zip to your sd card. Download root explorer, open it and select R/W . Navigate to the sd card and copy the new boot animation. Navigate to system/media and paste. It must be named bootanimation.zip.
If you want to change the boot image (first image you see at boot) that's a completely different process. Go here http://forum.xda-developers.com/archive/index.php/t-654042.html for a how to. I had a little trouble with this at first but got it to work. Scroll down and see my comment for a how to that worked for me.
Good luck!
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
Yes this is it. But all of the required files are not available for download. From what I gather I have to completely wipe my phone to unlock my HBOOT.
My HBOOT is S=ON I want the S-OFF bootloader but cannot find complete instruction/files to do so.
I'm ready to pull my hair out. I followed those steps for engeneering hboot to the letter... 2wice and it did not work. When pb001 is done flashing it sits at the hboot screen and still reads S-ON and when I try to flash a recovery from there it says "waiting for device" and nothing ever happens because the hboot screen is asking me to flash pb001 even though I already did. Those instructions are spectacularly bad. Does anyone have clearer or better instructions?
All this has done is waste an hr of my time and its making me see red.
Are you using the steps from this post? I was a little challenging at first however I was able to do it (more than once), although I was sad the first time that I had to re-flash the rom I was using and set up the phone all over again.
I no longer have a eris, however I will do what I can to help if you haven't already got it working.
shatterpoints said:
I'm ready to pull my hair out. I followed those steps for engeneering hboot to the letter... 2wice and it did not work. When pb001 is done flashing it sits at the hboot screen and still reads S-ON and when I try to flash a recovery from there it says "waiting for device" and nothing ever happens because the hboot screen is asking me to flash pb001 even though I already did. Those instructions are spectacularly bad. Does anyone have clearer or better instructions?
All this has done is waste an hr of my time and its making me see red.
Click to expand...
Click to collapse
Honestly, I don't know much about that because I rooted with the old method. What method did you use? Perhaps you can unroot and root with the old method (using cmd prompts to push custom recovery).
Sent from my Droid Eris using XDA App
If you don't already have it, download Titanium from the market. It's a great tool for backing up and restoring your phone.
Sent from my Droid Eris using XDA App
joshw0000 said:
Honestly, I don't know much about that because I rooted with the old method. What method did you use? Perhaps you can unroot and root with the old method (using cmd prompts to push custom recovery).
Sent from my Droid Eris using XDA App
Click to expand...
Click to collapse
I rooted with Eris one click. It gives you Amon's ra and I have several custom roms downloaded + I have a couple nadroid backups. I just can't figure out the engineering boot loader.
Flashing PB00 does unroot the phone so I'm not sure where to go from here.
shatterpoints said:
I rooted with Eris one click. It gives you Amon's ra and I have several custom roms downloaded + I have a couple nadroid backups. I just can't figure out the engineering boot loader.
Flashing PB00 does unroot the phone so I'm not sure where to go from here.
Click to expand...
Click to collapse
I am assuming you are following the guide here, for me it was confusing at step 5 in the beginning. Did you flash the engtools or push the flash image? Personally I pushed the flash tool.
Step 6 is tricky, you have to be patient as it does take a while and best to do it with plugged in. If I remember right it I did the very last step (flashing recovery.img) before rebooting when it asked me if I wanted to restart.
I lost root after doing it, however 1 click from the market was my friend and savior. I booted into bootloader and verified I had 1.49.2000 s=off, so it was worth it in the end.
At what point is it not working for you?
goldenstorm said:
I am assuming you are following the guide here, for me it was confusing at step 5 in the beginning. Did you flash the engtools or push the flash image? Personally I pushed the flash tool.
Step 6 is tricky, you have to be patient as it does take a while and best to do it with plugged in. If I remember right it I did the very last step (flashing recovery.img) before rebooting when it asked me if I wanted to restart.
I lost root after doing it, however 1 click from the market was my friend and savior. I booted into bootloader and verified I had 1.49.2000 s=off, so it was worth it in the end.
At what point is it not working for you?
Click to expand...
Click to collapse
Yes I am following Jcase's steps. I also flashed the image. When it asks me to reboot the boot loader it reboots to fastboot and does not ask me to install pb00 unless I go to HBOOT. When I flash PB00 in HBOOT it does so ok, but then it check's the sd card and keeps asking me to flash pb00 even though I already did. While in this screen I cannot see the device in adb or fastboot and I cannot flash a recovery to it. So all I can do is yank the Batt and boot to a unrooted 2.1 eris....
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
About offline flash I had the same problem that it couldn't connect to my device but when I used another computer it could find it.
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
You need a recovery.img from p769 and flash it through fastboot
Download https://mega.co.nz/#!7RxjnDyS!gYY7Zs6naT4fa3Oj1FfIFu2O_sfEtL1awPD-HOSOu_E
Then type in fastboot "fastboot flash recovery p4_769.img"
Sent from my LG-P769 using Tapatalk 4
I have the same issue adb won't connect no fastboot
Sent from my Amazon Kindle Fire using xda app-developers app
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again.
Some help on how to install fastboot
Did you install the omap4430 driver twice?
Open an elevated command prompt and type
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then open the Device Manager and see if you have the omap4 driver installed twice (in two locations)
Note: In Device Manager click the View tab and select Show hidden devices
If you don't see the omap driver installed twice, do this
Select the "other devices" and start deleting/uninstalling all of the devices you find here (I think the device you are looking for is "lg u2" but not 100% sure)
Once you have uninstalled all of the unknown drivers you found, run the start.bat again and follow the directions to flash the x & u img's (for your device).
Now go back to device manager and find the new unknown/other device created (should be lg u2) and install the omap4430 like you did the first time.
After you have done all this, rerun the start.bat and hopefully it will work for you.
Another thing, If you do see the omap driver installed twice, then it has to be your timing when you enter the battery. Keep trying different times to enter the battery
example. wait 1 second and enter battery, if that doesn't work wait 2 seconds then enter battery and etc.
Good luck
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
You were absolutely right, the issue was with having multiple drivers. I followed your steps and restored my phone to life. Thank you so much.
jlj012 said:
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
Click to expand...
Click to collapse
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
kuma82 said:
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
Click to expand...
Click to collapse
Lol..
Sent from my LG-P769 using Tapatalk 4
Got fastboot working, but now what?
kuma82 said:
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again
Click to expand...
Click to collapse
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
erraggy said:
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
Click to expand...
Click to collapse
To install custom rom or CM10 you need to unlock bootloader first. You should follow kuma82 in his post above to flash back stock rom.
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
kuma82 said:
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
Click to expand...
Click to collapse
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapatalk 4
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
I've been wanting to try this: go to your computer and check your device manager and disable the LG drivers then try the offline flash again. Kuma way works but it's very long, found this while I was reading but never tried for our phones. Same problem though as updating stops at 15 %
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
erraggy said:
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapa talk 4
Click to expand...
Click to collapse
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
Another thing, more than likely, after you flash with the r&d tool you will need to do a hard reset because you flashed cyanogen. Also, you will still need to root to fix the touch screen.
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
kuma82 said:
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
erraggy said:
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
Click to expand...
Click to collapse
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
THANKS!
Her phone had the stock TMOUS jelly bean ROM that we received OTA. I had only rooted her phone previous to my CM10.1 fiasco attempt.
So I've never flashed anything (successfully at least) on her phone. All of my previous android experience has been on 3 nexuses (One, S, 4) and my current HTC Sensation. That means I've only unlocked one bootloader that didn't support the fastboot oem method
I'm an experienced dev with the entire weekend to "play" with my daughter's p769
I also promise to provide lengthy posts in the Optimus L9 forums to help any future people from soft bricking any more devices.
Sent from my HTC Sensation using Tapatalk 4
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
kuma82 said:
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
UH OH... The "volume up" method isn't working on this device. I posted more details about it here. I'm beginning to think I may need to return the phone. I never thought flashing a ROM zip in CWM recovery could brick the phone. When I restoring the CWM backup also failed (when I at least was in CWM recovery which now is inaccessible), I freaked.
P.S. - I'm all out of thanks for the day. I think you got the lion's share though
Well guys, I think I messed this one up, Sprint HTC One Max that I unlocked the bootloader on and then proceeded to S-Off with Rumrunner and failed due to not already having su permissions.(note his instructions say "OR Bootloader unlocked" so I figured I was fine having done that) The device rebooted fine initially after exiting the tool and then after attempting to manually flash TWRP for this device so I could get root access and try again, the phone rebooted to recovery and now fastboot AC is as far as I can get. Downloading the Sprint Decrypted RUU from OMJ now because I'm retarded and cant figure out how to get around using commands in Free Arc to unzip the signed RUU...any help is appreciated. :silly: Tried manually updating the drivers for the "unknown device" on usb hub port 8 in my device manager with offical and generic HTC drivers and tried reinstalling HTC Sync to no avail. am I bricked?
Everyone MUST use the files for the HTC One "MAX" corresponding to their model (Sprint, Verizon or International). *OMJ has posted in our thread.
Use this:
http://forum.xda-developers.com/showthread.php?t=2525805
*Did you flash the twrp for the One MAX from this forum?
Jiggity Janx said:
Everyone MUST use the files for the HTC One "MAX" corresponding to their model (Sprint, Verizon or International). OMJ has not posted in any forum for the One MAX (as far as I know).
Use this:
http://forum.xda-developers.com/showthread.php?t=2525805
*Did you flash the twrp for the One MAX from this forum?
Click to expand...
Click to collapse
I have it, both the decrypted one OMJ posted on page 2 and the signed one. But free arc wont let me open it. What the hell am I doing wrong? How do I unzip the signed one and use it without the error. I know it has to be something simple I'm missing. Yes I used the twrpsprint.img from Squabbi's Toolkit, thats what failed the phone into recovery. (Red Traingle). Now the phone can get into the bootloader and it will boot into android but no usb debugging when I enable it.
Skyymiles said:
I have it, both the decrypted one OMJ posted on page 2 and the signed one. But free arc wont let me open it. What the hell am I doing wrong? How do I unzip the signed one and use it without the error. I know it has to be something simple I'm missing. Yes I used the twrpsprint.img from Squabbi's Toolkit, thats what failed the phone into recovery. (Red Traingle). Now the phone can get into the bootloader and it will boot into android but no usb debugging when I enable it.
Click to expand...
Click to collapse
Found OMJ post now. He posted the decrypted in the same thread as the encrypted. Got it.
Can you boot to bootloader with vol down and power? Does it show you as s-off?
Flashify in the play store will flash the twrp .img from flyhalf twrp thread in original dev or you can use his instructions and use fastboot.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
I don't think you need to ruu if you can boot to android and bootloader. It can be fixed using other methods.
Jiggity Janx said:
Found OMJ post now. He posted the decrypted in the same thread as the encrypted. Got it.
Can you boot to bootloader with vol down and power? Does it show you as s-off?
Flashify in the play store will flash the twrp .img from flyhalf twrp thread in original dev or you can use his instructions and use fastboot.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
I don't think you need to ruu if you can boot to android and bootloader. It can be fixed using other methods.
Click to expand...
Click to collapse
I can get to the bootloader no problems just that the phone wont talk to the computer. I can hear it connect/disconnect from usb but always device unrecognized so I cant send the phone any commands. I can boot into android no issues though. So youre suggesting flash twrp img using an app like flashify or goo manager like a openrecoveryscrript from android then install a custom ROM after to fix the fastboot usb recognition? I am S-On, unlocked currently.
I am hoping to help but was/am distracted. I think you can fix what is going on with flashing the twrp from flyhalf thread. I am not on sprint so haven't gone through it on that side.
Also as noted in the ruu thread you cannot flash the older ruu posted if you are on a newer update. Check the version.
do you have the htc drivers installed on your computer?
Maybe try to follow this to get back on track. It was written specifically with Sprint in mind.
http://forum.xda-developers.com/showthread.php?t=2550559
Jiggity Janx said:
Maybe try to follow this to get back on track. It was written specifically with Sprint in mind.
http://forum.xda-developers.com/showthread.php?t=2550559
Click to expand...
Click to collapse
I started here actually...lol Yes I just uninstalled them, disabled Antivirus, rebooted and freshly installed HTC Sync Manager with Drivers to make sure. If I can get an this app to flash TWRP and SU I may be in business...
UNINSTALL Sync manager, and just keep the drivers..
wase4711 said:
UNINSTALL Sync manager, and just keep the drivers..
Click to expand...
Click to collapse
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Skyymiles said:
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Click to expand...
Click to collapse
are you using adb commands to see if you are connected?
did you reboot your laptop and phone after installing the drivers?
antivirus and firewall off?
wase4711 said:
are you using adb commands to see if you are connected?
did you reboot your laptop and phone after installing the drivers?
Click to expand...
Click to collapse
yup.. going through troubleshooting this connection right now... nothing returned on adb devices, list of devices is blank. somethings up. no serial number, nothing... tried both in the OS and in fastboot.
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
at any rate I know adb works because it can see my old m7wls just fine.
Skyymiles said:
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Click to expand...
Click to collapse
Did the app "Flashify" from the play store not flash the twrp .img from fluhalf thread?
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
Update your version of adb. Older versions may not recognize devices on fastboot even though they do in adb.
Jiggity Janx said:
Did the app "Flashify" from the play store not flash the twrp .img from fluhalf thread?
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
Update your version of adb. Older versions may not recognize devices on fastboot even though they do in adb.
Click to expand...
Click to collapse
Never achieved SU to begin with so I cant flash it. the app FCs without Su permission. I'll try updating adb.
Question: If I never managed to achieve anything beyond Unlocking the bootloader, wouldn't a Factory Reset from the boot loader menu fix any partition discrepancies anyway and allow the PC to recognize the device again? I guess thats what I cant understand. What would go so wrong if I never flashed anything, not intended for Sprint HTC One Max's that would suddenly cause the PC not to recognize the Fastboot USB?
UPDATE1/25:
Updated everything in adb for 4.3 and 4.4 and 4.2.2 and the toolkits. Still nothing. I think I have determined the root cause may be a bad copy of TWRP that results in a QHSUSB_DLOAD issue like from the Evo 3D days. Unfortunately however, since the One Max is a relatively new device, there has been no "ultimate recovery tools" established to fix this type of error. So now, lol... wait for it. Now I have an "Unlocked", unrooted, S-ON, Stock HTC One Max(sprint) and stock recovery whos partitions I can only imagine are ok yet the computer refuses to recognize on fastboot.
That said, does anybody know, since I can apparently boot Android, and the phone itself works just fine, if there are any market apps which would support flashing from inside the phone, like Flash Image GUI to try and root this thing internally or am I just hosed/hard bricked stuck on stock?
Skyymiles said:
Never achieved SU to begin with so I cant flash it. the app FCs without Su permission. I'll try updating adb.
Question: If I never managed to achieve anything beyond Unlocking the bootloader, wouldn't a Factory Reset from the boot loader menu fix any partition discrepancies anyway and allow the PC to recognize the device again? I guess thats what I cant understand. What would go so wrong if I never flashed anything, not intended for Sprint HTC One Max's that would suddenly cause the PC not to recognize the Fastboot USB?
UPDATE1/25:
Updated everything in adb for 4.3 and 4.4 and 4.2.2 and the toolkits. Still nothing. I think I have determined the root cause may be a bad copy of TWRP that results in a QHSUSB_DLOAD issue like from the Evo 3D days. Unfortunately however, since the One Max is a relatively new device, there has been no "ultimate recovery tools" established to fix this type of error. So now, lol... wait for it. Now I have an "Unlocked", unrooted, S-ON, Stock HTC One Max(sprint) and stock recovery whos partitions I can only imagine are ok yet the computer refuses to recognize on fastboot.
That said, does anybody know, since I can apparently boot Android, and the phone itself works just fine, if there are any market apps which would support flashing from inside the phone, like Flash Image GUI to try and root this thing internally or am I just hosed/hard bricked stuck on stock?
Click to expand...
Click to collapse
Ok, Update 2! Managed to get into the Stock recovery console and wipe the cache partitions, but it seems even that did not fix the issue.(The phone had never been rooted or had a custom recovery flashed and got stuck on S-On, Unlocked, no recognition from Fastboot USB on the PC) So since I can apparently get here, can I flash a CWM or TWRP image from here(stock recovery->apply update from SD card or internal storage)? or is that only for flashing a whole ROM?
Thanks!!
Skyymiles said:
Ok, Update 2! Managed to get into the Stock recovery console and wipe the cache partitions, but it seems even that did not fix the issue.(The phone had never been rooted or had a custom recovery flashed and got stuck on S-On, Unlocked, no recognition from Fastboot USB on the PC) So since I can apparently get here, can I flash a CWM or TWRP image from here(stock recovery->apply update from SD card or internal storage)? or is that only for flashing a whole ROM?
Thanks!!
Click to expand...
Click to collapse
Ok, UPDATE 3, back at work trying a different computer... Turns out it wasnt as bad as I thought at all. Its a driver issue on my personal computer.(work computer recognizes the Max on Fastboot Usb, still didnt list it on devices yet but I'm not worried about that right now.) Oh well... so since I know this is an isolated incident, any recommendations for driver cleaner, like Drive Cleaner CC? Or what would be the best method short of wiping my laptop to a fresh copy of Win 7, that I could use to make sure I am removing all failing instances of HTC Drivers from my machine. Like I said it picks up and installs my HTC One (m7) fine, but the One Max, nadda. So I need to correct the driver issue on my end ultimately to reduce further issues. :silly: Sorry to keep posting to myself but hopefully someone else will benefit from reading what happened to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
Profit! Thanks to those who helped!!! Your comments were appreciated, mods can lock this thread as solved.
Sent from my HTC0P3P7 using xda app-developers app
Congrats! you seemed to have a long time fighting with the device.
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
UPDATE: [8/2/16] I have recompiled the binary with some fixes beaups made. These fixes should take care of the "samsung device only" error some are getting on 4.4 roms.
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
You must unzip the file first.
Download
Code:
adb push unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 unlock_n3
chown root.root unlock_n3
./unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Your the best. Trying it right now
Sent from my SM-N900V using Tapatalk
---------- Post added at 02:10 PM ---------- Previous post was at 01:58 PM ----------
ryanbg said:
Enjoy. Don't forget to thank @beaups too, he discovered the eMMC backdoor and exploited it!
Disclosure: I do not own a Note 3. The exploit happened to be applicable to the Note 3, and we compiled it for your devices rather than not release it at all. This seems like a reasonable and friendly thing to do for the community. I can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this. I am very familiar with Samsung however, and time permitting, will do my best to help anyone having issues.
You should not run this if you don't understand it.
ROOT REQUIRED, we aren't responsible for anything you do with this.
You NEED a MicroSD, and it WILL be formatted during this process.
YOU MUST DISABLE REACTIVATION LOCK OR YOU WILL HAVE ISSUES!!!!!!!!!
You can download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work.
The code below is NOT a script, you must enter the commands manually.
Code:
adb push samsung_unlock_n3 /data/local/tmp/
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n3
chown root.root samsung_unlock_n3
./samsung_unlock_n3
Allow device to reboot. After full reboot, run
Code:
adb shell
su
cd /data/local/tmp/
./samsung_unlock_n3
again, power down and pull battery. May need to run it again if it doesn't work after the battery pull.
Paypal: [email protected] [COMPLETELY VOLUNTARY AND OPTIONAL]
Click to expand...
Click to collapse
Perfect thanks so much ..this is tremendous [emoji120] [emoji120] donations are required. Donate to whom just breathed life into a great phone..Flashify idea by @alexp1289 was great idea to install recovery..this is f### ING awesome
Sent from my SM-N900V using Tapatalk
Awesome! Trying this now!
Cheers,
B.D.
God you are a life saver, I've been trying to get my uncle hooked up with a phone with a unlocked bootloader for awhile,
now he can use his current phone for it.
Does this work for v4.4.4 and 5.0?
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Do the commands HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
jellyhead said:
Does this work for v4.4.4 and 5.0?
Click to expand...
Click to collapse
Yes.
BackCheck said:
Any idea how long it takes on the first reboot? I assume it formats the SD card and that takes some time and I only have a 64gb card so I'm guessing I'll be looking at the Verizon logo a while.
Click to expand...
Click to collapse
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
Gl17ch said:
Do the command HAVE to be entered via adb? If I downloaded the zip to my phone, could I enter the commands through a terminal editor possibly?
Click to expand...
Click to collapse
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
tomixnscale89 said:
I'm confused. It asked me to run the binary again to finish the process, but when i did that, it tried to change the CID again. Am i doing something wrong? The CID has changed to the one it displays on cmd.
Click to expand...
Click to collapse
Do a battery pull and run the second step again. It will say "backing up loaders" when it is actually done.
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
It works, I have TWRP installed. I'll be divvying out donations come payday.
BackCheck said:
It works, I have TWRP installed. I'll be divvying out donations come payday.
Click to expand...
Click to collapse
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
ryanbg said:
Yes.
Try removing your SDCARD, boot up, and put it back in before you do it the second time.
You should do it with adb instead of terminal emulator. You could do it with terminal emulator, but I don't recommend it.
Click to expand...
Click to collapse
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
BackCheck said:
Flashify. It didn't look like they had much trouble getting it ported quickly for us. Now to get CM13 going but that'll be a little longer.
Click to expand...
Click to collapse
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
Yep just download the app and select the one in the pictures.
Download link for Flashify--
https://play.google.com/store/apps/details?id=com.cgollner.flashify
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900V using Tapatalk
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
I got sick of using dd to reinstall recoveries on my LG V500. There are one or two other apps I've seen that do this but this one always worked for me.
dreyeth said:
Sweet so that app auto flashes the recovery of your choice? and they have a TWRP port already for this?
I've always done it the manual way.
Thanks for the information.
Click to expand...
Click to collapse
https://twrp.me/devices/samsunggalaxynote3qualcomm.html
You still can download it manually. Read the notes and it shows the verizon note 3 supported.
Just confirmed good old "dd" method works fine and recovery boots nicely. Make sure you pick the correct version at the twrp website.
Now on to bigger and better things! Will donate!
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
dreyeth said:
Where did you get your TWRP build from?
The Note 3 Verizon hasn't had a unlocked bootloader until now, so I can't imagine there was a TWRP build ready for it.
Was there something close enough to be compatible, like a TWRP build for the developer edition?
Click to expand...
Click to collapse
I'm supposing that if I am running 5.0 the 4.4 TWRP will not work...
Once I get this to work will I be able to downgrade to 4.4/install a custom recovery/etc. ?
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
Sent from my SM-N900V using XDA-Developers mobile app
BostonDan said:
I tried this, and no change to my CID... It's still starts with 15...... I'm expecting it to start with 11 when it works.... Any ideas? I'm using an 8GB sd card, and the card was erased as expected....
My output was:
<begin output>
Do you understand the implications of these warnings?
(Yes/No)
Y
Type "Yes" or "No"
(Yes/No)
yes
[+] CID at boot time is/was: 15------------------------------
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
<end output>
I obfuscated the actual CID in the above output message. Is there any way to verify that this worked before I flash TWRP and possibly brick my device?
EDIT: Nevermind, I booted into download mode and found out that my device is seen as a "developer device". Anybody flash TWRP and CM13 yet?
Cheers,
B.D.
Click to expand...
Click to collapse
App flashify installs Twrp easy. All there no searching works beatiful
Sent from my SM-N900V using Tapatalk
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.