Related
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
I have installed the ICS V4 bootloader and everything is fine. (it has the big PASS thing). I can boot up to HC 3.2.1 fine as well.
However, when I go to press power+volume down, I get "booting from recovery kernal image" then it switches to a picture of the android with a caution sign.
Do I have to root my device and install CWM or something? (sorry I'm still quite noob at this, I haven't rooted yet). Didn't I already install this when I installed the bootloader?
Thanks in advance!
Booting stock HC and stock ICS after installation of ICS BL overwrites recovery.
Follow civatos guide for installing ICS BL V4:
http://forum.xda-developers.com/showthread.php?t=1622425
And do all the steps.
Greetings
edit: on Moscow's advice ;-)
HalloSpencer said:
Booting stock HC after installation of ICS BL overwrites recovery.
Follow civatos guide for installing ICS BL V4:
http://forum.xda-developers.com/showthread.php?t=1622425
And do all the steps.
Greetings
Click to expand...
Click to collapse
This includes Stock ICS Roms also
Thanks guys. I immediately booted to recovery after installing the bootloader. Now I have ICS running.
If I wanted to update to the V5 bootloader, could I do it without reinstalling my rom?
You guys are awesome
jgv115 said:
Thanks guys. I immediately booted to recovery after installing the bootloader. Now I have ICS running.
If I wanted to update to the V5 bootloader, could I do it without reinstalling my rom?
You guys are awesome
Click to expand...
Click to collapse
If I'm not mistaken, I believe you can put the v5 bootloader.blob in a flash.zip and flash through CWM. That's one method. This became available as of ver4.
The other would be to run the NVFlash again you used previously, and install only the bootloader (apx?). Your CWM and Rom should remain intact.
I use Blackthund3r's flash exe to install my .bin files. (gives some funny windows error but always completes) I just toss the new bootloader.bin in the same folder as the exe app. Also the latest recovery image. Do them both at the same time.
So basically 3 methods. Also, check your new UID number and make sure you convert it to SBK like you did the last time. ICS usually changes the UID number sometimes. I usually keep all UID's and SBK's written down.
Moscow Desire said:
If I'm not mistaken, I believe you can put the v5 bootloader.blob in a flash.zip and flash through CWM. That's one method. This became available as of ver4.
The other would be to run the NVFlash again you used previously, and install only the bootloader (apx?). Your CWM and Rom should remain intact.
I use Blackthund3r's flash exe to install my .bin files. (gives some funny windows error but always completes) I just toss the new bootloader.bin in the same folder as the exe app. Also the latest recovery image. Do them both at the same time.
So basically 3 methods. Also, check your new UID number and make sure you convert it to SBK like you did the last time. ICS usually changes the UID number sometimes. I usually keep all UID's and SBK's written down.
Click to expand...
Click to collapse
Can you pm me that windows error please? I think it's to do with my mode detection code being stopped abruptly but I want to have it fixed properly for v0.3.3
Sent from my Iconia A500 using Tapatalk 2
Hello people of the forum, I am newbie with android, I've been asking for help because my tablet stopped working after I followed a tutorial to route it, I used a program "Afterota v1" tutorial here on the forum in order to install APX more now I can no longer start, he did not ask to update.zip, I do not know what it ta asking update the screen as it is in the image Please someone help me to recover it.:crying:
the picture in this link, take the space, as I am new user can not post link, thanks
http : // img43.imageshack. us/img43/8262/a500c. jpg
jinhad said:
Hello people of the forum, I am newbie with android, I've been asking for help because my tablet stopped working after I followed a tutorial to route it, I used a program "Afterota v1" tutorial here on the forum in order to install APX more now I can no longer start, he did not ask to update.zip, I do not know what it ta asking update the screen as it is in the image Please someone help me to recover it.:crying:
the picture in this link, take the space, as I am new user can not post link, thanks
http : // img43.imageshack. us/img43/8262/a500c. jpg
Click to expand...
Click to collapse
the picture looks ok...
check your external sd card - make sure there is not an "update.zip" on that or your internal "sd card"
the writing you see on yr tab is ok you should be able to just
"reboot" the tab and be all good??
try running the afterOTA again....
PS >>> oh are you trying to flash the unlocked bootloader or rollback to HC??
dibb_nz said:
the picture looks ok...
check your external sd card - make sure there is not an "update.zip" on that or your internal "sd card"
the writing you see on yr tab is ok you should be able to just
"reboot" the tab and be all good??
try running the afterOTA again....
PS >>> oh are you trying to flash the unlocked bootloader or rollback to HC??
Click to expand...
Click to collapse
Thanks for responding:good:, so I've tried using afterOTA again, although not the usb connection. I was trying to put recovery_twrp_2.1.3-ICS.img with apx mode, it restarted and gave PASS screen, but now is only on this screen, asking "update.zip", already put in external SD: Acer_AV041_A500_1.031.00_WW_GEN1.zip, FLEX-Resurrection_Rev1-Aroma-Public.zip, cwm_hc_ics_root.zip, and nothing.
I have this information:
Tablet Cpuid: 037C624341E05557
Tablet Sbk: 0x17A51E00 0x94ABD401 0x7BE23003 0x340A2103
Android Build: Acer_AV041_A500_1.031.00_WW_GEN1
Bootloader: 00:03:12 ICS-
jinhad said:
Thanks for responding:good:, so I've tried using afterOTA again, although not the usb connection. I was trying to put recovery_twrp_2.1.3-ICS.img with apx mode, it restarted and gave PASS screen, but now is only on this screen, asking "update.zip", already put in external SD: Acer_AV041_A500_1.031.00_WW_GEN1.zip, FLEX-Resurrection_Rev1-Aroma-Public.zip, cwm_hc_ics_root.zip, and nothing.
I have this information:
Tablet Cpuid: 037C624341E05557
Tablet Sbk: 0x17A51E00 0x94ABD401 0x7BE23003 0x340A2103
Android Build: Acer_AV041_A500_1.031.00_WW_GEN1
Bootloader: 00:03:12 ICS-
Click to expand...
Click to collapse
Because, you still are running a stock rom,. more or less.
The problem happens, because you are re-booting after installing the custom recovery. And the rom you are running, is booting it to stock recovery (it's overwriting your custom recovery) which explains why it's looking for update.zip
What you need to do, is after installing your custom recovery, boot immediately to it Via adb, or shut down and boot using Vol- and PWR. Then install your custom rom.
MD
Moscow Desire said:
Because, you still are running a stock rom,. more or less.
The problem happens, because you are re-booting after installing the custom recovery. And the rom you are running, is booting it to stock recovery (it's overwriting your custom recovery) which explains why it's looking for update.zip
What you need to do, is after installing your custom recovery, boot immediately to it Via adb, or shut down and boot using Vol- and PWR. Then install your custom rom.
MD
Click to expand...
Click to collapse
I understand, I'm stuck in this mode, how can I do the adb, this procedure, detroit afterOTA the folder, I have a folder with adb is this?, as does the process? Thank you.
jinhad said:
I understand, I'm stuck in this mode, how can I do the adb, this procedure, detroit afterOTA the folder, I have a folder with adb is this?, as does the process? Thank you.
Click to expand...
Click to collapse
keep in mind that flashing custom roms and recovery's REQUIRE the unlocked bootloader be flashed FIRST... I'd suggest apxFlash tool to do that....all u need is in civatos bootloader thread, pls read very carefully. do the first 4 steps and then use apxFlash tool to complete the process....if u don't do things exactly as written you'll end up in trouble....
good luck
Sent from my GT-I9300 using Tapatalk 2
SOLVED
dibb_nz said:
keep in mind that flashing custom roms and recovery's REQUIRE the unlocked bootloader be flashed FIRST... I'd suggest apxFlash tool to do that....all u need is in civatos bootloader thread, pls read very carefully. do the first 4 steps and then use apxFlash tool to complete the process....if u don't do things exactly as written you'll end up in trouble....
good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend, I managed to solve reading .. is that as I am the brail, my english ta weak and had difficulty understanding, most did all the steps and got .. Thank you.
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery
Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?
yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock
e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?
Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app
Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.
wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it