[Q] How to Downgrade to 4.1.1 or Original for TF300T??? - Transformer TF300T General

Hey guys!
I am trying to downgrade my current Stock 4.2.1 Rom to either 4.1.1 or 4.1.2 either stock or custom if possible even factory original.
How would I go about doing this as there is no clear cut instructions I could find....not sure if I can use NVFlash???
I previously had root performed using the VoodooOTA Method. Now I have unlocked the bootloader and also managed to install the TWRP Custom Recovery....although I do not think it has been installed correctly as it is unable to mount certain directories...../cache or /data and /system are some examples.....not sure if that is because of version or because of changes done to root enabler by new firmware upgrade.
If anyone has clear instructions or could point me in the right direction I would highly appreciate it!
Thanks

There might be a few issues with the new OTA update and recovery, if you already have a backup with nvflash from when you had ICS then yes there is a guide you can use to go back,
http://forum.xda-developers.com/showthread.php?t=1894867
if not then you should either try to flash one of the stock ROMs mentioned in the sticky in the Android Development section
http://forum.xda-developers.com/showthread.php?t=1697227
or if you think twrp is not working well you should wait just in case you do damage to your device. There is a chance some partitions have been altered in the new update and twrp needs to be updated, by whoever is responsible for our version, to be able to function properly.
If the reason you want to go back is the launcher then there is an option to switch to the 4.1 launcher in the options, not sure where exactly but if you look a bit further down in this section you'll find someone else posting something about it.
And a last suggestion is that when you have a question better post it in the appropriate section
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app

hahahaha! funny u mention that coz i think I screwed up :silly: ...What I did was download the official bootloader from the Asus Website ASUS Transformer Pad TF300T Firmware: V10.4.2.20 Only for US SKU (Android 4.1) and use fastboot to flash the blob file.....now the only thing it does is spin at ASUS (boot loop)....The funny thing is it did affect how the fast boot option loads though it now shows up with the option of USB....and does not automatically go to fastboot.....my comp recognizes both in fastboot and adb the device so there is something......just performed a cache and dalvik wipe but to no vail and prior did a fix permission.....ALSO I do not receive any error with regards to mounting like before....
btw....which section would this fall under??? Development?

OKAY!!!!!! Im back in business.....WOOT!!! It worked just had to perform a factory reset to stop boot loop

rakesh219 said:
btw....which section would this fall under??? Development?
Click to expand...
Click to collapse
this belongs to the q&a section
rakesh219 said:
OKAY!!!!!! Im back in business.....WOOT!!! It worked just had to perform a factory reset to stop boot loop
Click to expand...
Click to collapse
Glad you fixed it but try not to do things you're not sure of in the future so as not to brick it :victory:

Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium

ilyuha1108 said:
Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium
Click to expand...
Click to collapse
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.

Yup sure can do it just give me a few hours trying to fix the dishwasher :good:

rakesh219 said:
Yup sure can do it just give me a few hours trying to fix the dishwasher :good:
Click to expand...
Click to collapse
any chance your running WW and not US and could now grab us the WW OTA update file

ilyuha1108 said:
Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium
Click to expand...
Click to collapse
Ashcunak said:
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.
Click to expand...
Click to collapse
I am pretty sure he said that he is unlocked and running twrp, you can flash whatever rom you want from recovery but it will not bring back the ICS bootloader and the ability to have NVFLASH or even the 4.1 BL, so in reality he flashed a new rom and not actually downgrade to the previous state of the tablet.

Ashcunak said:
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.
Click to expand...
Click to collapse
crossmission said:
I am pretty sure he said that he is unlocked and running twrp, you can flash whatever rom you want from recovery but it will not bring back the ICS bootloader and the ability to have NVFLASH or even the 4.1 BL, so in reality he flashed a new rom and not actually downgrade to the previous state of the tablet.
Click to expand...
Click to collapse
That is actually correct, I dont know if itwill work in general but I previously had my OS rooted and backed up using Voodoo OTA Rootkeeper. The only thing that I did new from here on is
1. Backup an Nandroid using ADB Terminal Access -
Code:
adb backup –apk –shared –all –f C:\Android_Asus_4-2-1.ab
Ofcourse in-order to perform this feat you would need Android SDK Tools Package and Google USB Drivers installed on the drive
2. Perform the unlock bootloader using the apk found on the Asus Website
3. Flash Stock Rom that can be downloaded from Asus or here
using fastboot
4. Flash TWRP for JB using fast boot with help of link
5. Go into recovery Wipe Dalvik and Cache and Factory Restore
6. And boot!
Okay I know this is no GUIDE as I am press with time....I will try to make a proper one. but in all honesty I would just wait for the REAL DEV's to post the solution to 4.2.1

rakesh219 said:
That is actually correct, I dont know if itwill work in general but I previously had my OS rooted and backed up using Voodoo OTA Rootkeeper. The only thing that I did new from here on is
1. Backup an Nandroid using ADB Terminal Access -
Code:
adb backup –apk –shared –all –f C:\Android_Asus_4-2-1.ab
Ofcourse in-order to perform this feat you would need Android SDK Tools Package and Google USB Drivers installed on the drive
2. Perform the unlock bootloader using the apk found on the Asus Website
3. Flash Stock Rom that can be downloaded from Asus or here
using fastboot
4. Flash TWRP for JB using fast boot with help of link
5. Go into recovery Wipe Dalvik and Cache and Factory Restore
6. And boot!
Okay I know this is no GUIDE as I am press with time....I will try to make a proper one. but in all honesty I would just wait for the REAL DEV's to post the solution to 4.2.1
Click to expand...
Click to collapse
Hi,
I need to downgrade my tab as my touch doesn't work and need to flash other firmware it. It was told to me to downgrade and it should work, but was said I need TWRP because with CWM I could brick my tab. Without touch it's impossible to use TWRP. I have ulocked bootloader and rooted. Your guide doesn't seem to need of use exactly TWRP as Wipe Dalvik and Cache is worked when I rooted tab.

Related

[TIPS AND DISCUSS] ICS update DOES NOT *ALWAYS* BREAK ROOT (& other tips and reviews)

[TIPS AND DISCUSS] ICS update DOES NOT *ALWAYS* BREAK ROOT (& other tips and reviews)
This is not intended to be a bug-sharing thread, report them if you wish, but I'm sure there will be entire threads devoted to this, so keep this in mind when posting.
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
Click to expand...
Click to collapse
Cheers luna ... just need a WW version
Noob question though ..... I am on a custom ROM. I have CWM recovery.
I thought I couldnt update OTA if my TF was rooted ? or is it that I have the custom recovery that prevents this ?
I can flash back to stock easily - its removing CWM and unrooting that looked to be the more techie issue.
With what you are saying is there an easy way, once I have reverted to stock ROM, to revert to stock recovery without losing root ? Or do i even need to revert to stock ROM ??
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
another question, i cannot root with nachoroot, so is it possible to root with 1-click root?
asder00 said:
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
Click to expand...
Click to collapse
That might work, I don't know exactly because I got the FOTA pushed to my device and updated through the 'official' update process. I honestly have no idea how the dlpkgfile is even packaged, if it is CWM flashable or requires stock recovery etc., honestly my first time fooling with capturing the OTA files.
Ok I'm trying and I will tell u....
I don't care about root right now...
luna_c666 said:
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
Click to expand...
Click to collapse
Do I understand correctly that I only have to do Step 7 of the tutorial? and then install ICS (regular update process)?
I am rooted and I have CWM (no custom ROM)
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Dreamboxuser said:
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Unfortunately I never did get around to trying the latest Spark, I saw the complaints about touchscreen issues and decided it might be best to wait for Paul to work it out, but Asus finally got the upper hand on him!
Seems a treat, but I expected as you can see I've been running CM9 on my epic for about 3 weeks now. Much snappier, generic comments that have already been posted- but not explored completely yet, too busy helping others get their own ICS since the update came in to be selfish and sign off yet
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
luna_c666 said:
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
Click to expand...
Click to collapse
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Steven_nl said:
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Click to expand...
Click to collapse
Yes, your apps and data should remain intact, and that is correct, you only need to flash the recovery back to stock if you are already on a stock ROM. As of right now, only US and TW firmware versions are getting the OTA pushed to their device, but if you are not one of these you can manually flash to these stock ROMs via CWM if need be. But yes, if you are stock + root + CWM, you only need to flash over CWM back to stock. Root is fine to keep and all data will be saved (it is an official update, people would be irate if it wiped their data you know!)
Great stuff thanks again. I'n in Europe so I might need to wait for a bit but that is fine.
No problem. Ok guys, I've done a bunch of talking and answered quite a few PMs, and posted all my methods/experience with ICS so far, now, I'm going to go play for a while (it's 7am, and I've not been to bed, and I have to work at 4pm and my son will likely be up in an hour, so no sleep for me today, should have a well-rounded review by the time you see me again)
If you guys want to keep this thread alive, have at it! Turn it into a discussion.. See you guys in a while, can't wait to see what I miss while I'm gone
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
dmazyn said:
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
Click to expand...
Click to collapse
If you are SBK1 device you can flash CWM via NVFlash, use CWM to flash SU binary from ChainsDD (located HERE ) and then flash the stock recovery if you so choose to return to stock recovery (in case any patches or incremental updates come out you may need this if you want to stay stock ICS).
ONE MORE THING BEFORE I GO GUYS;
I just noticed that ICS brings a new recovery as well, so the update will overwrite your recovery, I assume it will do this if you figure out how to flash via CWM so be prepared for that. Any devs will want to work on removing the recovery blob from the patch file before releasing as a CWM flashable zip. My 2 cents. See you guys in a few hours/days, depending on how addicted I get to ICS.
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
asder00 said:
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
Click to expand...
Click to collapse
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Confirmed working! thanks. too bad i have to go straight to work
Dreamboxuser said:
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Ur right but i prefer to wait for ww
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried.
Click to expand...
Click to collapse
After I updated to ICS, OTA Rootkeeper gave me the option to Restore root. Under the status section, Device rooted and Root permission granted were both unchecked until I used the Restore root option.

help! about factory image ota

fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.
sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.

Any Guide available For Flashing 4.2.2 on Custom kernel without Loosing Data

As the Topic Suggest is there any guide someone made for noobs like me
who wanna upgrade there NEXUS 7 to 4.2.2 having Custom kernel without loosing data ?
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you don't have to wipe anything. Just flash and go!
scream4cheese said:
You don't need a guide in your case.
Click here:
http://forum.xda-developers.com/showthread.php?t=2148337
There are two STOCK 4.2.2 roms in this thread. One is DEODEXED and the other is ODEXED.
I recommend downloading the DEODEXED STOCK 4.2.2 rom.
Here's the link to the DEODEXED STOCK ROM:
http://goo.im/devs/teshxx/Nexus7Wifi/Grouper-JDQ39_4.2.2-Deodex_Rooted-02-14-13-teshxx.zip
Download it, put it in your N7 and flash it via recovery. You won't lose any data and you won't have to wipe anything. Just flash and go!
Click to expand...
Click to collapse
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
1) make a full nandroid (cwm/twrp) backup
2) flash a 4.2.2 stock-derived ROM on top of existing ROM - no wipe
2.5) flash a minimal root kit (SuperSU or Superuser) if not in ROM in step 2 - no wipe
3) flash the same kernel you used previously - no wipe
4) profit!
No workie? Restore backup from step # 1 and try something else.
pleasant said:
I won't get error 7 ?
For installing this ?
And its not ota update how come it wont wipe data?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
There's no need to do that. But in spite of it, I can tell you that you can just create the nandroid backup and leave it in your device. Don't pull it out. Just flash the download in my previous post and if anything goes wrong. Enter recovery mode and restore your system. Even if you did pull the nandriod backup file from the N7 and the device fails to boot up, you cant just put the file back in to restore it that way. It won't mount so you can access the internal storage system.
P.S i don't know how to make the backup show up but i think there are a few thread here that some people have found a solution to it.
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
pleasant said:
For safety I made a full online nandroid backup as above suggested now the issue is I am trying to copy the backup on PC
But when I plug nexus 7 on PC
In clockworkmod folder the backup folder doesn't show up but in
File manager at tablet shows it :/
Click to expand...
Click to collapse
I have had TWRP behave the same way - sometimes it will put backups in
/data/media/TWRP/...
and sometimes in
/data/media/0/TWRP/...
It is a bit of a mystery what causes this to happen. Strangely, when there is a folder in the first location, TWRP (2.4.1.0) will not find the second one. But, if I manually move the files from the first location (/data/media/TWRP) to the second location (/data/media/0/TWRP) using a file manager, then TWRP will find the backups no problem.
well, the "sdcard" mount point ( == /data/media/0/ ) is the thing that shows up on the PC via MTP mode, so I would just move the files to the second location. I'm not sure if CWM behaves the same way, but you will certainly be able to copy them from the N7 to the PC at that point.
good luck.
pleasant said:
DA FAAK this thing worked :good:
i am finally upgraded to 4.2.2
tell me why this one didnt gave "7" error ?
Where this Guide was Hiding i have been looking for easiest method and this is what it is
Click to expand...
Click to collapse
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
scream4cheese said:
LOL. I told you it works.
There's one thing that you're missing from that update. And that is the bootloader version, the bootloader version that you're currently using is 4.13. The newest version is 4.18. You don't have to update it if you don't want to.
I'll include this link for you to flash the latest bootloader via command prompt.
http://forum.xda-developers.com/showthread.php?t=2150251
I hope you know how to use adb/fastboot.
Click to expand...
Click to collapse
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
pleasant said:
first tell me does updating bootloader wipes data ?
and secondly what does bootloader do and advantage of updating bootloader ?
u mean to say sideload command ?
Click to expand...
Click to collapse
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
boot(basically kernel) and system are usually what people mean 'custom ROM'. So if you just manually flash these two things(and usually need to be done together), none of your 'data' would be lost.
So just find these two images (usually .img) in whatever custom ROM you want and flash it.
This is the unix convention for a long long while and android is just linux
scream4cheese said:
Updating bootloader does not wipe anything. It simply replaces and updates the one you already have on.
Definition of a bootloader:
http://m.androidcentral.com/what-is-android-bootloader
Sideload? I think so.
Click to expand...
Click to collapse
So if there is a flashable zip available that would be great
Sent from my Nexus 7 using Tapatalk HD
you don't really need to flash bootloader
chimpanzeexda said:
you don't really need to flash bootloader
Click to expand...
Click to collapse
Yeah, I told him that.
Sent from my Nexus 7 using Tapatalk HD
scream4cheese said:
1. Have you read the thread?
2. No it won't give you an error. Why would it?
3. It's from the official OTA update. You just don't need to wipe anything. Trust me on this.
4. How come? I did this last night on my Nexus 7 and everything is just fine.
5. You won't get a bootloop or an error if you do exactly what I just told you.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hi bro can you provide me the similar flashable zip for android 4.3 for nexus 7 wifi
Sent from my Nexus 7 using Tapatalk HD

[Q] Flashed 4.2.2 rom on 4.2.1 ... now what?

It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

Categories

Resources