Database Info

[Q] is there a way to unroot and lock the bootloader again ?

is there a way to unroot and lock the bootloader again ?

quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.

but as of now no way to flash the stock recovery

slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.

distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery

slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !

distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?

quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.

slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.

distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery

slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).

distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse

quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod

got it all working now thanks to you and distortedloop .
thanks a lot guys.

Neither Win7 nor Mint recognise TF101 by USB since updating to ICS

I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?

+1
But since i transfer my data via Dock/USB it's not a big issue atm.

jordivf said:
I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?
Click to expand...
Click to collapse
My B50 was recognized by Win7 after successfully installing the device driver. A TF101 Drive was created with SD and External Storage available. I have a stock ICS, no root and no custom roms.

Mine did to. Although I had to go into device manager and uninstall the replug mine in and they reinstalled themselves. All but one that I can remember off hand but I just double-clicked it and it installed the 2nd time.

I had same issue... if you used CWM flashable package, you need to reflash bootloader. I've found link in dev section. From then everything is just fine.
Sent from my ICS TF101 by XDA HD app

You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
reupload: http://www.mediafire.com/?h4pgduf8zsgmh96
E: gnufabio (Revolver ROM) use this boot image in his ROM, I think you can use this package for your US version TF

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.

josteink said:
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.
Click to expand...
Click to collapse
It was the WW version I tried but still no joy.

michael_duvalle said:
It was the WW version I tried but still no joy.
Click to expand...
Click to collapse
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)

josteink said:
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)
Click to expand...
Click to collapse
Yes. I was originally on Prime 2.1.0, flashed ww-9.2.1.11-CWM-full-rooted.zip, then flashed ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip on top. No wipes were performed and everything else except the battery usage is working properly.

jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
You, Sir, are a genius.
Yup! That sorted the issue.

michael_duvalle said:
Yes. I was originally on Prime 2.1.0,
Click to expand...
Click to collapse
No wipes were performed
Click to expand...
Click to collapse
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.

schauol1 said:
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.
Click to expand...
Click to collapse
What would be the best way to fix this then. Should I revert to Honeycomb stock and update the official way or shall I just wipe and reflash ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip. Also, If I did the second method, what exactly should I wipe?
Cheers

michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.

jozka.1 said:
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.
Click to expand...
Click to collapse
When you mean extract blob from the zip and place to the root of SD, do you mean the internal SD or the Removable SD?

It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)

jozka.1 said:
It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)
Click to expand...
Click to collapse
I tried it in terminal and it said that the file was written in several seconds. Several minutes later I went back to it, rebooted and still no joy.

And before boot system did you saw flash new blob file?

jozka.1 said:
And before boot system did you saw flash new blob file?
Click to expand...
Click to collapse
Yes. I left terminal open for about 10 minutes, then rebooted.

[ToolKit] Nexus 7 one click root tool !

This tool will root you nexus 7 install su or super su and ClockWorkMod recovery!!
i already developed a similar tool for the nexus s and galaxy nexus,this tool is based on the same code with few modifications.it should root your device in few minutes,so give it a spin and tell me how it goes
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current v1.5:http://d-h.st/xMX
Mirror:http://www.mediafire.com/?c29tr726xpejad7
(old versions)
v1.1: http://d-h.st/8I4
HOW-TO
Click to expand...
Click to collapse
Extract the downloaded zip file on your pc,install the drivers available in the "drivers" folder if you don't have them already installed,after installing the drivers run the file called "root.exe" to root your device.
and here is a video that explains it all (big thank to SladeNoctics) : http://www.youtube.com/watch?v=2Q6uBd38hm0&feature=youtu.be
Changelog
Click to expand...
Click to collapse
v1.5
-updated superuser and supersu
-new recovery (all cwm bugs should be fixed)
-new menu that

Well I am impressed. I thought for sure I would be seeing it AFTER it was shipped.
Good job!

also do i need android sdk installed for this toolkit to work?

If you have an android device, installing the android sdk or not should not be a question. It's always recommended having it on your PC.

Darn, you beat me to it.

Hrm...there are a lot of ways you could improve this.

This does unlock your device but it didn't root it. I tried Super USer & SuperSU option & both didn't root my device. Even though the dialog box says your device is rooted but it didn't root. My device would stay in fastboot screen forever & I would have to do a hard reboot (hold on to the power button). For root, I had to do "adb reboot recovery" & flash the SU zip file.
Thanks for your work!

movieaddict said:
also do i need android sdk installed for this toolkit to work?
Click to expand...
Click to collapse
it's better to install it,but you just need the device driver for this to work
RMXO said:
This does unlock your device but it didn't root it. I tried Super USer & SuperSU option & both didn't root my device. Even though the dialog box says your device is rooted but it didn't root. My device would stay in fastboot screen forever & I would have to do a hard reboot (hold on to the power button). For root, I had to do "adb reboot recovery" & flash the SU zip file.
Thanks for your work!
Click to expand...
Click to collapse
well that's weird,it should work unless their is a problem with the recovery am using (it's not booting or flashing),can you check please if the su you are using (superuser or supersu) is getting pushed to your tab ? you should see it in your file manager in /sdcard/,from what you said i see that the recovery flashed but it didn't boot this why you had to boot it manually and flash su.(note that i don't have the nexus 7 so i didn't test this completely,i tested this on a nexus s by replacing the recovery with a nexus s one to assure their nothing wrong with the script)
also can anyone confirm this issue ? and if anybody rooted successfully with this please confirm,thanks

Whoooooo... Already there is a Way to root the Nexus 7!? :what:
Send from my LG GT540 Android 4.0.3 Polishblood PreRC CM9

m.sabra said:
well that's weird,it should work unless their is a problem with the recovery am using (it's not booting or flashing),can you check please if the su you are using (superuser or supersu) is getting pushed to your tab ? you should see it in your file manager in /sdcard/,from what you said i see that the recovery flashed but it didn't boot this why you had to boot it manually and flash su.(note that i don't have the nexus 7 so i didn't test this completely,i tested this on a nexus s by replacing the recovery with a nexus s one to assure their nothing wrong with the script)
also can anyone confirm this issue ? and if anybody rooted successfully with this please confirm,thanks
Click to expand...
Click to collapse
Yes, superuser & SuperSU is pushed to sdcard

damn, you beat me too it. I was writing a script as we speak... :'( haha.

Great job can't wait to get mine shipped to me :thumbup:

Wow. That was fast. Lol
-Sent From My Little Phoney-

FadedLite said:
damn, you beat me too it. I was writing a script as we speak... :'( haha.
Click to expand...
Click to collapse
DeamonFish said:
Darn, you beat me to it.
Click to expand...
Click to collapse
can i get a cookie
RMXO said:
Yes, superuser & SuperSU is pushed to sdcard
Click to expand...
Click to collapse
well that solved a part of the thing,can you try something for me ? take the recovery from the tool folder and try using this command with fastboot while you are in the bootloader (you can get there using 'adb reboot bootloader' ) use this command to boot the recovery 'fastboot boot cwm.img' and tell me what happens,btw have you tried re-running the tool ?
could you please try it ? thanks in advance

This worked PERFECTLY! As long as one follows the directions... it should work just fine. I would love to give a donation for your time. Thanks again!!!! Now to get OTG working.
UPDATE: Spoke too soon. Root/CWM didn't stick. Finished the process using the info on this post: http://rootzwiki.com/topic/28585-cwmeasyroot-nexus-7/
I'm still very grateful because I wasn't able to get the phone unlocked before using this tool. Thanks again!

jdavet said:
This worked PERFECTLY! As long as one follows the directions... it should work just fine. I would love to give a donation for your time. Thanks again!!!! Now to get OTG working.
UPDATE: Spoke too soon. Root/CWM didn't stick. Finished the process using the info on this post: http://rootzwiki.com/topic/28585-cwmeasyroot-nexus-7/
I'm still very grateful because I wasn't able to get the phone unlocked before using this tool. Thanks again!
Click to expand...
Click to collapse
thanks for your feedback ! i understand that the tablet rooted but the only problem was cwm not sticking,am working on a fix now and should upload soon,thanks for feedback again

Wow this is great! Can't wait to get my nexus 7 . But i have a question, are there still issues with Clockworkmod? like the charging issue?

m.sabra said:
thanks for your feedback ! i understand that the tablet rooted but the only problem was cwm not sticking,am working on a fix now and should upload soon,thanks for feedback again
Click to expand...
Click to collapse
Thanks for the great work. Looking forward to the fix.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

verison 1.1 released !, this should fix the issue making the recovery not sticking,meaning the tablet will no longer revert to stock recovery after reboots,this work is currently based on user feedback,my other tool,and root guides,i should get my nexus 7 tab soon so i will be able to test by myself until then i would be very thankful for your feedbacks and reporting any issues
thanks
link to v1.1: http://d-h.st/8I4

wow 1.1 alrerady many thanks :good:

[Q] twrp wont install roms

i just installed twrp 2.4.1.0 and every time i tried to flash a rom it said that it failed. i looked around the thread and people were having the same problem. they said to go back to 2.3.3.0 so i did. it still wont work. before i installed 2.4.1.0 i was on a version i couldnt flash the 4.2 roms with, i have baked blackbean 6 and used the terminal emulator to update. i just typed su then dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 like it said on the website. and i did rename it to twrp.blob and i got the jb version .blob file.i also still can boot up blackbean. sorry for the trouble im kinda new at this stuff.

I had that too. Problems went away when I unticked "signature verification" or something like that in TWRP (it's in the same screen where you swipe to confirm the flash).
Hope that helps :good:

Ti2 said:
I had that too. Problems went away when I unticked "signature verification" or something like that in TWRP (it's in the same screen where you swipe to confirm the flash).
Hope that helps :good:
Click to expand...
Click to collapse
thanks ill try that

Report back whether it helped

Ti2 said:
Report back whether it helped
Click to expand...
Click to collapse
nope it still dont work. i keep getting error status 7. should i try to reflsah it except use fsatboot. ive been useing terminal emulator for it. and i looked threw the settings in twrp and none of the boxes are checked. in the mount only cache and dalvic are checked.

What bootloader are you on?

Ti2 said:
What bootloader are you on?
Click to expand...
Click to collapse
im on the jellybean bootloader.

What rom are you trying to flash?

Ti2 said:
What rom are you trying to flash?
Click to expand...
Click to collapse
cm 10.1

Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?

sbdags said:
Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?
Click to expand...
Click to collapse
I'm getting Status 7 with the latest tf300t ROM from get.cm and the latest TWRP

sbdags said:
Status 7 usually means your device Id is not compatible with the ROM you are trying to flash. What ROM are you currently on and where did you DL cm from?
Click to expand...
Click to collapse
im on blackbean 6 and i got it from the link in the thread

well i think i found the problem i was looking threw my downloads on my pc and i found twrp for the tf300tg. i have the tf300t. and that would explain the error 7 thing with the device id. im downloading the right one right now and ill reply back if it works or not.

yupp that fixed it. i feel dumb now lol

How did you get blackbean 6 to flash,I've been trying to flash 6 for days and keep getting that status7 thing.I don't want blackbean 7 cause directory bind doesn't work with 4.2 jb.I have jb bootloader with newest twrp.My error was the build prop one but I have tf300t and my build prop is tf300t.I've been reading forums for days trying to get the error7 gone.II even deleted the build prop check thing in the script updater in the rom zip file.After doing that I now get status 6 error.I ve tried almost every stock based rom for tf300t and had no problem flashing,even blackbean7 flashes fine.Any help would really be appreciated.Thanks or if anyone knows a work aroundto get directory bind to work with jb 4.2. I have like 27 gigs of game data for all my games

Recovery Question

I read that many people are very pleased with Phil's recovery, and I'm a bit noob so I'd like to understand some thing:
1)I'm now on scanno twrp and kikat cm11-10012014, and can I install it via terminal emulator?
2)If I install it will I be able to go from Cromi-x to CM11 without the need to change recovery?
3)I understand that twrp is not that safe with cm11, and many people get bricked devices...is Phil's cwm more safe?

aplopeanu said:
I read that many people are very pleased with Phil's recovery, and I'm a bit noob so I'd like to understand some thing:
1)I'm now on scanno twrp and kikat cm11-10012014, and can I install it via terminal emulator?
2)If I install it will I be able to go from Cromi-x to CM11 without the need to change recovery?
3)I understand that twrp is not that safe with cm11, and many people get bricked devices...is Phil's cwm more safe?
Click to expand...
Click to collapse
1.) Yes:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
2.)You can change the recovery when switching or remove the assert line from the updater-script of the zip.
3.) I'm not sure. Only one person bricked (who double posted and I assumed was two different people).

cmendonc2 said:
1.) Yes:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
2.)You can change the recovery when switching or remove the assert line from the updater-script of the zip.
3.) I'm not sure. Only one person bricked (who double posted and I assumed was two different people).
Click to expand...
Click to collapse
Well chrmhoffmann said yesterday he had continuous reboot in recovery...I updated today kernel without any problem but I don't have nvflash and i really need a working tablet at a high level, which I had this month...
Did you update CM11 lately? Have you had any problem? And on which verion are you now?

aplopeanu said:
Well chrmhoffmann said yesterday he had continuous reboot in recovery...I updated today kernel without any problem but I don't have nvflash and i really need a working tablet at a high level, which I had this month...
Did you update CM11 lately? Have you had any problem? And on which verion are you now?
Click to expand...
Click to collapse
I am using the nightly from January 10th, which seems relatively stable. I usually only update once a month or if something big comes out.

cmendonc2 said:
I am using the nightly from January 10th, which seems relatively stable. I usually only update once a month or if something big comes out.
Click to expand...
Click to collapse
I use the same...well for now I'll stick with Twrp and if more people complia I'll change it...but I'm pretty sure that guy who brciked his device did something bad too but he didn't said...or maybe it was just the way he entered recovery...we'll see... thanks a lot for all the info you are extremely helpfull in this community