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....
Related
Unlocked, rooted and S-ON. I can get into Fastboot, and I'm trying to get into recovery. I can't. It just reboots to the white HTC screen and sits there. Same with Factory Reset.
Everything I do with Hasoon's kit fails. Either the device is never found, or I get this-
sending 'recovery' (6346 KB)... FAILED (status malformed (1 bytes))
I simply can't get into recovery.
I've taken zip files of RUU's, recoveries, kernels and everything, renamed them to PH85IMG.zip and tried loading. They just go through the loader icon on the top left, then returns back to fastboot. I'm just not getting nowhere. I've been on the forums searching for several hours now.
HBOOT recognizes when USB is plugged in. But the phone is never found when I run commands from the toolkit.
I put my SIM in my old iPhone2 while I try to get this working. It's a horrible phone!
What else should I try?
RobsSXT said:
Unlocked, rooted and S-ON. I can get into Fastboot, and I'm trying to get into recovery. I can't. It just reboots to the white HTC screen and sits there. Same with Factory Reset.
Everything I do with Hasoon's kit fails. Either the device is never found, or I get this-
sending 'recovery' (6346 KB)... FAILED (status malformed (1 bytes))
I simply can't get into recovery.
I've taken zip files of RUU's, recoveries, kernels and everything, renamed them to PH85IMG.zip and tried loading. They just go through the loader icon on the top left, then returns back to fastboot. I'm just not getting nowhere. I've been on the forums searching for several hours now.
HBOOT recognizes when USB is plugged in. But the phone is never found when I run commands from the toolkit.
I put my SIM in my old iPhone2 while I try to get this working. It's a horrible phone!
What else should I try?
Click to expand...
Click to collapse
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Yes you have to be in fast boot in order to use hansoons tool kit... And yet to flash your recovery again (I suggest 4ext) then use the toolkit to boot into recovery using the shortcut commands
Sent from my HTC Ruby using xda premium
Keylogger_0 said:
The toolkit cannot send commands through hboot, only fastboot. You have to boot into hboot and then select the fastboot option
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Awesome, thanks. I don't remember having this much trouble last spring when I rooted and unlocked this phone. It went really smooth.
I'm having a really hard time right now with it. I can't get any OS to load. I can load Recovery, but then 4EXT won't mount SD card.
Anyone see this before?
{
"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"
}
If I can get myself out of this mess, I don't think I'm going to hack my phones anymore. I'm not on top of it enough.
RobsSXT said:
Awesome, thanks. I don't remember having this much trouble last spring when I rooted and unlocked this phone. It went really smooth.
I'm having a really hard time right now with it. I can't get any OS to load. I can load Recovery, but then 4EXT won't mount SD card.
Anyone see this before?
If I can get myself out of this mess, I don't think I'm going to hack my phones anymore. I'm not on top of it enough.
Click to expand...
Click to collapse
Will it let u format the internal sd?
sent from my
NRGized amaze
powered by Faux
aj_2423 said:
Will it let u format the internal sd?
Click to expand...
Click to collapse
No, on that screen I just posted it- it shuts down right there (I took that a millisecond before it shut down). Then it reboots to the white screen where it just hangs.
EDIT
I got this working to this point. Just dealing with the new issue-
Error mounting /internal_sdcard!
Searching forums now...........
RobsSXT said:
No, on that screen I just posted it- it shuts down right there (I took that a millisecond before it shut down). Then it reboots to the white screen where it just hangs.
EDIT
I got this working to this point. Just dealing with the new issue-
Error mounting /internal_sdcard!
Searching forums now...........
Click to expand...
Click to collapse
Do you know how to use adb? Well, if not, you're gonna need to.
boot into recovery and WHILE it's loading, input this command in the command prompt window EXACTLY as it is presented! Meaning that if a letter is capitalized, you need to do so too. For best results, I recommend copying the command in its entirety and paste it in the prompt.
The command is as follows:
adb shell /sbin/newfs_msdos -F 32 -L INT_SD -c 64 /dev/block/mmcblk0p36
It should spit out some stuff, that is usually normal, and then in the prompt, also type in:
adb reboot-recovery
after that, your woes should be gone.
EDIT: You should, however, reinstall whatever ROM you were using. This trick only fixes the internal SDCard.
Keylogger_0 said:
Do you know how to use adb? Well, if not, you're gonna need to.
Click to expand...
Click to collapse
Thanks. I got familiar with ADB. I put in your commands in the command prompt, and not only were your instructions easy to read and follow, but it worked. My SD card is now readable. I also cleaned all my caches and re-partitioned the card. 4EXT is working 100% and all is well.
I downloaded the Fourth Bar: Infusion ROM and installed it through the 4EXT. It seemed to work- I was provided with several options to choose from in terms of defaults (kernel, boot animation, launcher, camera, lockscreen, etc), however the actual install happened way too fast. I left all of the options as default. Before I knew it, the install was done and rebooting. However, it went back to the white screen where it sat there and didn't budge. I left it for over 10 minutes.
I have tried both the stock kernel and the Faux kernel, neither make a difference.
RobsSXT said:
Thanks. I got familiar with ADB. I put in your commands in the command prompt, and not only were your instructions easy to read and follow, but it worked. My SD card is now readable. I also cleaned all my caches and re-partitioned the card. 4EXT is working 100% and all is well.
I downloaded the Fourth Bar: Infusion ROM and installed it through the 4EXT. It seemed to work- I was provided with several options to choose from in terms of defaults (kernel, boot animation, launcher, camera, lockscreen, etc), however the actual install happened way too fast. I left all of the options as default. Before I knew it, the install was done and rebooting. However, it went back to the white screen where it sat there and didn't budge. I left it for over 10 minutes.
I have tried both the stock kernel and the Faux kernel, neither make a difference.
Click to expand...
Click to collapse
You may have to mount the /data and /system partitions in recovery as writable
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
You may have to mount the /data and /system partitions in recovery as writable
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
Good idea. Here's what I did.
In Mounts | Storage I have /data, /internal/sdcard, /sdcard plus others.
When I load into Mounts| Storage, they are ALL unmounted except /cache. So I go and mount them all.
Install the OS from .zip and it does it's thing.
Reboot, and hangs at white screen.
OR
Don't reboot, and go back to Mounts | Storage, and /sdcard needs to be mounted again.
If I reboot, all need to be mounted again except for /cache.
I doing some searches, I read that maybe my SD card needs formatting, or there's a format issue. I have run a few formats of my card and checked it's health, and it seems okay.
RobsSXT said:
Good idea. Here's what I did.
In Mounts | Storage I have /data, /internal/sdcard, /sdcard plus others.
When I load into Mounts| Storage, they are ALL unmounted except /cache. So I go and mount them all.
Install the OS from .zip and it does it's thing.
Reboot, and hangs at white screen.
OR
Don't reboot, and go back to Mounts | Storage, and /sdcard needs to be mounted again.
If I reboot, all need to be mounted again except for /cache.
I doing some searches, I read that maybe my SD card needs formatting, or there's a format issue. I have run a few formats of my card and checked it's health, and it seems okay.
Click to expand...
Click to collapse
Another possibility is that the recovery got glitchy. Maybe reinstall 4EXT recovery and make sure the smart flash thing is enabled.
Sent from my Amaze using xda app-developers app
I got the OS to load. I ran all the format options in 4EXT (every option available).
When I rebooted, it loaded the OS.
Finally.
im having the similar problem but mine constantly reboots every 5 seconds is there any fix
{
"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"
}
Jelly Bean Anyone???
That's right, in case you didn't know, a Jelly Bean OTA was "accidentally" pushed out to lots of people on Christmas Eve. Maybe you grabbed it, maybe you didn't. Well for those of you that didn't, I have quite the surprise for you today!!!
Here it is, the "accidental" Jelly Bean OTA!!!!!
Let's go through the steps to get this on your phone. Now keep in mind, just to test out these instructions, I've done this myself since I am back on the RAZR now!
CAUTION!!!!! AFTER INSTALLING THIS UPDATE, IT IS COMPLETELY IMPOSSIBLE TO GO BACK TO ICS!!! YOU HAVE BEEN WARNED!!
Note: I am absolutely NOT responsible for anything that happens to your phone during this process.
Prerequisites:
1. Download the Jelly Bean update file and place it on the root of your external sdcard (root of sdcard means DO NOT put it in any folders, just put it on the main part of the external sdcard.) http://d-h.st/8l1
2. Download and install Winrar (free version) http://www.rarlab.com/download.htm
3. Download Mattlgroff's RAZR Utility v1.82 http://batakang.com/ftp/DROID_RAZR/DroidRazrUtility1.82.zip
4. Download and install Voodoo OTA Rootkeeper from the Play Store https://play.google.com/store/apps/...m9yZy5wcm9qZWN0dm9vZG9vLm90YXJvb3RrZWVwZXIiXQ
Update your SU Binary before backing up your root!
Install Instructions:
1. Find the zip file for the RAZR utility you just downloaded and right click on it. Select "Extract Files..." then click OK.
2. Connect your phone to your PC with a USB Cable in FASTBOOT MODE.
3. Go to the extracted folder from the Utility and double click the DroidRAZRUtility.bat file.
4. Select option 1 to fastboot back to complete stock .211 (Note: If you're just on stock rooted .211 with NO RECOVERY, skip this step. If the update fails, fastboot back to .211)
5. After fastbooting back (it will take a while) Reopen the DroidRAZRUtility.bat file.
6. Stay connected to your PC, with your phone ON normally, change the USB connection to MTP Mode, now go to Settings > Developer Options, and turn on USB Debugging.
7. Use the DroidRAZRUtility.bat file again, this time select Option 2 which will root your .211 build.
7a. Open the app drawer on your phone, navigate to SuperUser, open the app, and update your su binaries.
8. Open the app drawer on your phone and navigate to the Voodoo OTA Rootkeeper App and open the app.
9. Once the app is open, allow it Superuser Permission, then select "Protect Root."
10. Reboot Device
11. Go back to the OTA Rootkeeper App and this time select "Temp Unroot."
12. Turn your phone off. Once powered down, press and hold the power button + volume down at the same for about 9 seconds, when the screen flickers, release the buttons and quickly press all 3 side buttons (power, vol+, vol-)
13. You're now in the bootloader, press the vol- button to highlight "Recovery" and press vol+ to select it.
14. You'll be greeted with an Android on his back, press both volume buttons at the same time here to enter stock moto recovery.
15. Now in stock recovey, select "install update from external sdcard."
16. Wait for the update to finish installing (about 20-30 minutes.)
17. After the update is finished, simply reboot the phone.
18. Congratualtions!!! You now have stock Jelly Bean on your RAZR!!!
Now let's get your root permissions back!
1. Reboot your phone normally after the update finishes installing.
2. Open the Voodoo OTA Rootkeeper App
3. Select "Restore Root."
4. PROFIT!
IF YOU HAVE TROUBLE RESTORING ROOT AFTER THIS UPDATE, TRY THIS TOOL (made by mattlgroff) BEFORE DOING ANYTHING ELSE!!!!!!!
Try this tool and let me know if it works please.
Extract to desktop
Make sure you have the drivers installed
Connect phone to PC
Enable USB Debugging
Double click the FixRoot.bat file
http://d-h.st/nep
Not making any promises but it might work.
VIDEO of Jelly Bean 4.1.2 on the Motorola Droid RAZR courtesy of Tomsgt:
http://youtu.be/iLDnG0ZqxTI
ROOT ACHIEVED FOR JELLY BEAN!!!!!!!!!!
Credit to whoever found the exploit and whoever posted the topic at droidrzr.
http://www.droidrzr.com/index.php/topic/6924-root-achieved-for-jb-ota-razrmaxx-xt912/
I know that there are other threads like this one, but I honestly thought mine was a little easier to understand and a little more in laymen terms. If any Mods want this removed, please feel free to do so!
seems very simple (affecting other partitions? I mean the other ROMs installed?)
thanks
Doesn't matter, people don't really use search function.
It maybe possible to get root back by temp downgrade to ICS kernel.
I'll only reveal it when JB for umts_spyder is official.
Requirement :
- CID partition backup. So backup now before you lose root.
Code:
dd if=/dev/block/mmcblk1p18 of=/sdcard/cid.img
#It just 512kb (2kb compressed)
whirleyes said:
Doesn't matter, people don't really use search function. I add some delicious info.
It maybe possible to get root back by temp downgrade to ICS kernel.
I'll only reveal it when JB for umts_spyder is official.
Requirement :
- CID partition backup. So backup now before you lose root.
Code:
dd if=/dev/block/mmcblkp18 of=/sdcard/cid.img
#It just 512kb (2kb compressed)
Click to expand...
Click to collapse
you just miss a "1" mmcblk1p18
thank you whirleyes for your find , i'm looking forward to see it
sevenup30 said:
you just miss a "1" mmcblk1p18
thank you whirleyes for your find , i'm looking forward to see it
Click to expand...
Click to collapse
Opps. It maybe doesn't work for XT912. I take back my word.
But it never hurt to have a CID backup.
whirleyes said:
Opps. It maybe doesn't work for XT912. I take back my word.
But it never hurt to have a CID backup.
Click to expand...
Click to collapse
Lol only 1 way to find out.
Sent from my DROID RAZR using Tapatalk 2
I have read alot about this new JB leak. And as i understand it is for xt912 (USA). Will this work for xt910 (Nordic)? Or maybe it will flash but will not give me signal.
Jelly Bean video if anyone is interested
http://youtu.be/iLDnG0ZqxTI
TeddyOFLove said:
I have read alot about this new JB leak. And as i understand it is for xt912 (USA). Will this work for xt910 (Nordic)? Or maybe it will flash but will not give me signal.
Click to expand...
Click to collapse
I stand corrected, you can download it from here and try to flash: http://forum.xda-developers.com/showthread.php?t=2068716
Tomsgt said:
Jelly Bean video if anyone is interested
http://youtu.be/iLDnG0ZqxTI
Click to expand...
Click to collapse
Thank you! Added to the OP!
won't boot..
Hey guys, I ran into an issue while doing this for my brother. Once I installed the stock ICS via the tool in the OP, the phone will only boot to the motorola screen and then the phone goes completely black and will not boot. I can still get into fastboot, but if I try to reach recovery I get the droid with the red exclamation mark (so it seems the phone now has no recovery on it). I have tried redoing the process, but I'm getting the same result once the flash is complete.
Any advice on what I should do? Was using a fully charged CDMA RAZR fyi..
I appreciate any help on this and I'll be the first to admit that I almost always run into problems with Motorola phones. Is there another method or toolkit to simply get back to a bootable phone and try my luck again?
Thanks!
Does this work on a gsm xt910?? I am using stock rom but have a safestrap within so any help on what i can do!?!?
Sent from my XT910 using xda app-developers app
Nevermind.. I used RSD to flash the ICS stock. I suppose I can now go through the rest of the process in the OP?
Seems to be working fine now, so I'll continue the rest of the steps to get root and flash JB tonight. Please let me know if I'm missing anything and thanks again for any advice / suggestions.
Jikenda said:
Hey guys, I ran into an issue while doing this for my brother. Once I installed the stock ICS via the tool in the OP, the phone will only boot to the motorola screen and then the phone goes completely black and will not boot. I can still get into fastboot, but if I try to reach recovery I get the droid with the red exclamation mark (so it seems the phone now has no recovery on it). I have tried redoing the process, but I'm getting the same result once the flash is complete.
Any advice on what I should do? Was using a fully charged CDMA RAZR fyi..
I appreciate any help on this and I'll be the first to admit that I almost always run into problems with Motorola phones. Is there another method or toolkit to simply get back to a bootable phone and try my luck again?
Thanks!
Click to expand...
Click to collapse
When you see the little Android with the exclamation point, as stated in step 14:
14. You'll be greeted with an Android on his back, press both volume buttons at the same time here to enter stock moto recovery.
Irthu said:
Does this work on a gsm xt910?? I am using stock rom but have a safestrap within so any help on what i can do!?!?
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
Look for the process to install this in a thread made by whirleyes, this is for CDMA ONLY.
Jikenda said:
Nevermind.. I used RSD to flash the ICS stock. I suppose I can now go through the rest of the process in the OP?
Seems to be working fine now, so I'll continue the rest of the steps to get root and flash JB tonight. Please let me know if I'm missing anything and thanks again for any advice / suggestions.
Click to expand...
Click to collapse
Thank you. This is perfect. I tried many different threads with different processes, but this is the only one that got it working.
Thanks for all your work.
eaglesbaby said:
Thank you. This is perfect. I tried many different threads with different processes, but this is the only one that got it working.
Thanks for all your work.
Click to expand...
Click to collapse
Very welcome!
Sent from my DROID RAZR using Tapatalk 2
Lost root
Hi guys,
So I successfully updated to JB using the method in this thread, but now it appears that I've lost root, even though I used VooDoo and everything. Has anyone else run into this?
Shawna
waiting for GSM update
eaglesbaby said:
Hi guys,
So I successfully updated to JB using the method in this thread, but now it appears that I've lost root, even though I used VooDoo and everything. Has anyone else run into this?
Shawna
Click to expand...
Click to collapse
Voodoo worked fine for me but i have a tool I'm going to post that should help everyone.
s27moto said:
waiting for GSM update
Click to expand...
Click to collapse
Wrong thread, this is CDMA. Whirleyes already posted GSM instructions.
Sent from my DROID RAZR using Tapatalk 2
eaglesbaby said:
Hi guys,
So I successfully updated to JB using the method in this thread, but now it appears that I've lost root, even though I used VooDoo and everything. Has anyone else run into this?
Shawna
Click to expand...
Click to collapse
Try this tool and let me know if it works please.
Extract to desktop
Make sure you have the drivers installed
Connect phone to PC
Enable USB Debugging
Double click the FixRoot.bat file
http://d-h.st/nep
Not making any promises but it might work.
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.
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.