Related
Hey i'm trying to root my Rogers Dream via this method...
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)
My problem is after completing the whole process I am still not rooted.
I think that nothing happens when i do this part...
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
are there suppost to be messages after I type those in?
Basically after the whole process i can't get into recovery, and i do not have su permissions.
Thanks for any insight!
For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery
Thanks I'll give those a try anyways heres the fixed link
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)
e334 said:
For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery
Click to expand...
Click to collapse
Ok the unlockr method does not work for me.
The HTC Dream is not on the compatible list for oneclickroot can anyone confirm it working?
Where can I find RC7?
have you tryed this app
http://forum.xda-developers.com/showthread.php?t=747598
just install it with a file manager and run it and you should be rooted after that download rom manager from market and install a custom recovery from there
^__^
I finally managed to get the custom recovery flashed! thanks to the xda guide
http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
If I managed to flash the recovery, does that mean i have root?
Can someone please explain how to do this part? I just get an error...
run the following two fastboot commands (this will prevent issues flashing your rom)
fastboot erase system -w
fastboot erase boot
Click to expand...
Click to collapse
Will anything happen if I do not do this step?
EDIT: Seems I have root now after the app root, flashed cyanogen waiting for it to boot.
aw man you just destroyed my will live.
I was reading this entire post with intense anticipation and was thoroughly let down when I did not see you post a successful root
Any updates on this?
I just purchased a Rogers Dream to learn about rooting and to play with.
If you did have success with this tutorial could you let me know? http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
I was considering following this tutorial myself!
Cheers
@bourne-nolonger
I used that method a little while ago with no issues.
The steps are easy to follow and work without issue.
Yes i was successful with XDAs procedure
My will was almost destroyed... i traded my magic for this dream... but now im happy
awsome!
thanks for the feedback guys.
definitely looking forward to finally getting a chance to root my G1.
Will report my results!
Cheers
quick question.
in the wiki under "D - Installing an engineering SPL" step 11 says to
Code:
"powerdown - fastboot oem powerdown"
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Sorry I should also ask: Can I follow the wiki that describes how to flash CM5+ to flash CM6.1.0? Is the process the same basically between the two versions of CM?
I want to try 6.1.0 instead of going with 5+
Cheers
bourne-nolonger said:
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Click to expand...
Click to collapse
That is because its the oem command and the second option (powerdown) is up to the phone to parse..
Once you run 'fastboot erase system -w' and return to recovery you can install any rom you wish just make sure you have an ebi1 kernel.
You also may wish to check out the 2708+ compatible kernel thread to get some extra ram, warning however if you are a rogers customer you will need to sign the e911 wavier before you can switch to any other radio otherwise they will cut your data service.. if you are with another carrier there is no such requirement.
Thanks for explaining step 11. Not sure I fully understand, but I'll do some additional reading.
I was looking at some of your threads before. I thought the 15mb ram expansion wasn't available for the rogers dream?
This is my first time flashing, could I flash cm first then maybe try yours later?
The g1i have luckily isn't my main phone. I bought it just to get comfortable with rooting and flashing.
Cheers
Sent from my Nexus One using Tapatalk
I managed to successfully root and flash CM6 onto my G1.
I see why people were complaining about performance issues.
Its a little sluggish, but usable (mind you are I am not using this as my daily phone)
thanks to XDA for a beginners guide to rooting this phone!
sorry bout this guys but im just curious.. i thought rc7 was for europe only... i honestly am confused now lol i know for me its rc29 im in america and you are in canada is the device really that different even though its such a short distance..? i apologize if its a stupid question...
I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?
I had a similar issue a couple days ago, problem I think was due to TWRP not having "RT -RM" (? - sorry I'm not looking at the exact text right now or have it memorized) option checked in Settings in TWRP, or possibly due to issue of older TWRP version, .2 and the newer .3 works better. My System directory was unmounted and couldn't come back, stuck in boot-loop until I followed the revert-to-stock directions. I had to download the 2 gig file, taking about 2 hours, and it contained readme.txt w/ instructions and all files needed to revert, but it was very tricky. A .DLL must be overwritten in Windows to get the LG firmware flashing software to work right, and you need the .TOT file. It will work if you are diligent, so don't give up hope. I thought my bada$$ new phone was bricked but finally got it to flash back to stock using that method, possibly similar to the quote in this thread, http://forum.xda-developers.com/showpost.php?p=48434571&postcount=1150, using Verizon instructions / sprint files. You can get it back. Mod will probably lock this thread as it is not development so follow that post I just linked, along with the OP. I am in Windows 8.1 x64 so I think it can work on any version of Windows.
Oh and this thread should probably get locked as it shouldn't go in dev section, mod will probably move or lock it. Hope you figured it out.
Sent from my LG-LS980 using Tapatalk
Thread Moved as it does not belong in the Development Section.
What I did ti fix diwnload mode
I took the rom I last flashed. Opened it. went to the system folder and extracted the build.prop (opened it with notepad). Press the find button in one of the drop down menus and find the model number your g2 thinks it is and change it to what it actually is.( in my cause mines had a d801 rom so it thought was one instead of an ls980) I changed mine from d801 to ls980. Saved it (make sure its saved as build.prop). Now go into the rom you originally got the build.prop from and replace it with the new one adb push the rom to the phone in twrp then flash it. Then boot into download mode and flash away
viper42391 said:
I hit the update tonight not thinking and before I had disabled Xposed.. Now my phone is stuck in a boot loop to TWRP. I have tried to wipe dalvik and cache, tried the adb shell commands that work for most people, tried to restore a backup, but none have worked so far.
I am trying to download the stock file to revert back to stock, but it says it will take 2 hours. Any help for the weary?
Is this the only way to get it working again?
Click to expand...
Click to collapse
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
NBreunig3 said:
Go into twrp, Go to advanced, Go to terminal, Click the arrow,in bottom right.
Enter
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Hit enter then enter this dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Hit enter and reboot
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much! Work great!
I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?
Mortred said:
I am dealing with the same issue,
i've had the Optimus ROM installed
and decided to try out cloudy, the phone was rooted and unlocked.
after wiping in TWRP and installing the new rom phone fails to boot to system and goes to recovery automaticly.
i know i could fix this by installing everything from scratch (STOCK).
NBreunig3's solution doesnt work for me either.
what am i doing wrong in the process?
Click to expand...
Click to collapse
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.
vPro97 said:
Save the headache, flash stock 4.4.2, towelroot, autorec and start over.
Click to expand...
Click to collapse
Yeah that is exactly what i did (used ioroot25, and the autorec app is amazing!!), but since i didnt have anything installed on my pc i had to download everything from scratch
and a simple 20 min process became a multiple hours one (trying to avoid that in the future).
anyway i've got the cloudy ROM now and it seems that it is already unlocked so i got that going for me which is nice .
Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Mlight123 said:
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Click to expand...
Click to collapse
Sadly, I just joined your club!! lol I wanted to comment here incase anyone else can help us or if I manage to figure it out myself I can find this thread easily. I got it rooted with newest version of Kingroot too, then I used Supersume to update to SuperSU and everything was working fine. When I tried rebooting, same thing as you I presume, I get kernel is not se enforcing I think it said and got the dreaded Unauthorized software was found running on this device, please take to att for service.
Sorry I can't help with your current problem. But, did you ever try to reboot with the kingroot SU?
This is definitely a slippery slope with no installation image.
moonbutt74 said:
Reboot to recovery, connect to pc and via adb shell , do a manual unroot.
that usually consists of
adb shell mount /system
adb shell rm /system/xbin/su
adb shell rm -fr /system/bin/.ext <----.ext is a directory
adb shell ls -al /system/bin/app_*
lrwxrwxrwx root root 2014-06-30 09:42 app_process -> /system/xbin/daemonsu
lrwxrwxrwx root root 2014-06-30 09:42 app_process32 -> /system/xbin/daemonsu <---remove this symlink
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process32_original <---- rename to app_process32
-rwxr-xr-x root shell 73508 2008-08-01 08:00 app_process32_xposed <------ not there if you don't have xposed
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process_init
Then search /data/app /system/app and /system/priv-app and remove the offending apk's base directory.
m
Click to expand...
Click to collapse
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Mlight123 said:
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Click to expand...
Click to collapse
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Shocked...
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Mlight123 said:
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Click to expand...
Click to collapse
Glad to hear it worked for you mate! Sadly, it didnt for me. I do have good news of my own though, I was able to have my wife take it by the local Best buy store and after they tried the normal factory reset and such, he must have had an Odin flashable 5.1.1 file or something because the tab is back to working order.
That is how I knew I was in trouble after I rebooted the first time after installing Kingroot and Supersume Pro. I also got the red lettered "Kernel is not SEandroid enforcing in top left corner too, but the next thing I saw was the " Unauthorized software detected, please power off and take to ATT ". I don't think I ever even made it to the samsung screen if my memory is correct (It might not be! lol) It sounds like either kingroot or SuperSU left something behind after install maybe? If you go to Settings > About tablet > Status and scroll all the way to bottom, the last entry says custom as well correct? The unlocked padlock on boot just means Syscope is detecting something not official installed somewhere it normally shouldn't be.
I just kept to odin folder and boot(LP_fix).tar on my pc because despite getting stuck in a boot loop you lose root after you fix it so it's kind of like a tethered root lol
Guys Iam having this same problem but I don't speak computer lingo can another walk be though step by step so I can fix my tablet?
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
I had this same problem, I just ended up giving up, exchanging tablet for a new one. :c
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
That's exactly the problem i had. But when i took it to best buy, they said that, their software cannot read my tablet, because of "an abnormal software has been found on this device" its probably because my tablet is custom...Any Fixes?
Can't you guys boot to download mode and flash the stock files via odin?
wp4jot said:
Can't you guys boot to download mode and flash the stock files via odin?
Click to expand...
Click to collapse
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
How about this?
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
wp4jot said:
How about this?
http://forum.xda-developers.com/showpost.php?p=65481346&postcount=606
Click to expand...
Click to collapse
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Definitely worth trying. It's a bricked phone and there's nothing to loose.
thisisapoorusernamechoice said:
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Click to expand...
Click to collapse
wp4jot said:
Definitely worth trying. It's a bricked phone and there's nothing to loose.
Click to expand...
Click to collapse
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
thisisapoorusernamechoice said:
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Click to expand...
Click to collapse
wp4jot said:
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
Click to expand...
Click to collapse
I figured, no worries, just didn't want to confuse anyone else :good:
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.