Hi all!
I want try 2.1 on my DE Dell Streak. The problem is, that i can not write any (!!!) recovery. I have rooted the device with universal root and my build is 6267. If i try to write the recovery with fastboot it says "Okay" but whenever i press the up+down volume buttons i see only the old recovery.
Any ideas?
crazy cat said:
Hi all!
I want try 2.1 on my DE Dell Streak. The problem is, that i can not write any (!!!) recovery. I have rooted the device with universal root and my build is 6267. If i try to write the recovery with fastboot it says "Okay" but whenever i press the up+down volume buttons i see only the old recovery.
Any ideas?
Click to expand...
Click to collapse
What recovery are you using? If its clockworkmod then it looks like the standard recovery but you have to select option 2 - update software with update.pkg - press the camera button and it will go into the clockwork mod recovery.
Radddogg said:
What recovery are you using? If its clockworkmod then it looks like the standard recovery but you have to select option 2 - update software with update.pkg - press the camera button and it will go into the clockwork mod recovery.
Click to expand...
Click to collapse
I tried the the ClockWorkMod 2.5.0.1
Does it realy looks like the standard recovery?
crazy cat said:
I tried the the ClockWorkMod 2.5.0.1
Does it realy looks like the standard recovery?
Click to expand...
Click to collapse
No it looks like clockwokmod recovery but to get into it you have to go through the stock recovery. Just do as I said and the screen should go blank for a few seconds then the clockworkmod recovery should appear.
What I mean is the stock recovery loads up then you select option 2 and it then loads up clockworkmod, so it looks at first like it has not worked. I flashed mine three times before someone pointed this out to me.
Hm...Ok
Waiting now for 10 mins, but nothing hapens on the black screen in front of me. I will reboot my device and try flashing it onece again.
Realy strange. Is tere no solution, that works at first time?
crazy cat said:
Hm...Ok
Waiting now for 10 mins, but nothing hapens on the black screen in front of me. I will reboot my device and try flashing it onece again.
Realy strange. Is tere no solution, that works at first time?
Click to expand...
Click to collapse
Try THIS version, that's what worked for me.
Or try the attached file, I've just flashed this and it worked first time
try erasing recovery first
fards said:
try erasing recovery first
Click to expand...
Click to collapse
This was it!
I see now ClockworkMod. Can you tell me what this is:
E:Can´t find MISC:
E:Can´t find MISC:
ClockworkMod Recovery v1.8.1.7
E:Can´t find MISC:
Click to expand...
Click to collapse
l clockwork mod isn't 100% compatible with steak
Ignore warning
Ok, fine. Thank you so much!
Related
Hello all
I am having a small issue with GTab
I can reboot into recovery every time from the power and volume+ combination, but sometime will not reboot if I go to the menu and reboot (power-off) menu, or if I go into CWM ROM Manger and reboot to recovery. sometimes I get the in and other time just reboots everything comes up. just like rebooting from the menu at time quicker..
I am running CWM v.8 Vegtab 7.1.0
now I believe this start after I flashed from CWM ROM Manger the a version CWM .. can remember the version (sorry ) screen was Orange and had the logo CWM in the center.. this is when I noticed the problem, then I reflashed back to V.8 thinking that would fix the problem and it did not.
I hoping this make sense I know it not world stopping or fun stopping, but it is a pain..
hoping someone had seen this problem before.. and could give me some direction to look at
Jim
1. Using the Power and Vol + key is the recommended method to boot into recovery. Avoid using the other methods.
2. Uninstall ROM Manager. It works fine on phones, but, is known to cause problems on the gTab.
3. Make sure both your ROM and your CWM are built for your bootloader (1.1 or 1.2). Since you said you have VEGAn-Tab 7.1.0, you can find out the version of your bootloader using the info. in this thread.
Suggestions:
1. Copy the zip file in post #3 of this thread to the SD card and then "install" it (once) using CWM.
2. If you're on a 1.1 bootloader, these CWM versions are available: CWM-2.5.1.1-bekit-0.8 and CWM-4.0.1.5
If you have the 1.2 bootloader install one of these CWM versions: CWM-3.0.2.8 or CWM-4.0.1.5. All are available on this board. Do a search.
thanks rajeevvp
I am using bootloader 1.1
every step worked great.. you are cool android person..
went with CWM-2.5.1.1-bekit-0.8 since that what I had in the first place
Are there any pluses going to CWM-4.0.1.5?
thanks for your help again..
Jim
jweir said:
Are there any pluses going to CWM-4.0.1.5?
Click to expand...
Click to collapse
I like that it tries to use the external SD card first and only then falls back to using the internal one for backups, restores and update.zip installs. Other than that and the new menu colours, there aren't a lot of externally visible differences.
More info. in this thread.
rajeevvp,
thanks for the information.. about version of CWM.. I think I found the one that will not work with the reboot menu "power off" menu.. I have installed CWM-4.0.1.5 and tried the menu option and also running GScript to reboot in recovery mode and will not do it all the time with 4.0.1.5.
what happen is that is just boots normal, which is not a bad thing.
and I know you do not like the idea of going into recovery mode without doing the power and volume + method.
just thought you would like to know what I found out.
thanks again for all your help..
Now if I want to go back to bekit-0.8 would you I need to do the erase misc like I did before?
Jim
jweir said:
I think I found the one that will not work with the reboot menu "power off" menu.. I have installed CWM-4.0.1.5 and tried the menu option and also running GScript to reboot in recovery mode and will not do it all the time with 4.0.1.5.
Click to expand...
Click to collapse
I didn't understand this. Are you saying that CWM-4.0.1.5 does not do "Reboot recovery" correctly everytime? And the ROM also? Both should usually work (but, I don't recommend it) on the 1.1 bootloader.
Now if I want to go back to bekit-0.8 would you I need to do the erase misc like I did before?
Click to expand...
Click to collapse
No need. Erase misc only if you get stuck on the 3 birds or if you go into a reboots-into-recovery loop--both of which are unlikely given your CWM (bekit-0.8 or 4.0.1.5) and bootloader (1.1) versions.
rajeevvp,
Sorry for the late Reply..
only it I use Gscript reboot to recovery, Menu from the shutdown .. Select reboot and then either reboot or reboot recovery.. if I am using CWM-4.0.1.5 with VegenTab 7.1.0
I can always go in to recovery mode from the volume and power button combination.
using bekit-0.8 I can get it to reboot into recovery from anywhere..
yes, I thought it was werid too..
thanks for all your help
Jim
I don't recommend doing "Reboot to recovery" using any tool--GScript, the ROM option, or the CWM menu item. Your tablet may "hang" at the 3 birds splash screen or go into a "always-reboot-into-recovery" boot loop.
Few days back my mobile was alnost bricked, it was on fastboot mode.. but thnx to a xda thread due to which i was able to un-brick my p500...
But in this process, i had to flash AmonRa recovery (because the cwm recovery file i downloaded was corrupt)... now my mobile is running very smoothly as it used to..
But i want CWM recovery, not AmonRa as i don't like it at all and i am not comfortable with it at all..
Can anyone help please ...
install from ROM Manager
dhruv.always said:
install from ROM Manager
Click to expand...
Click to collapse
flashing cwm recovery over AmonRa recovery directly using rom manager might just brick my device... plz tell me a safe solution.
Sent from my LG-P500 using xda premium
emergency mode > flash only recovery (CWM) to Program LGMDP THUNDER v1.5 ...by Notonlyeyes
u.bindal said:
Few days back my mobile was alnost bricked, it was on fastboot mode.. but thnx to a xda thread due to which i was able to un-brick my p500...
But in this process, i had to flash Aroma recovery (because the cwm recovery file i downloaded was corrupt)... now my mobile is running very smoothly as it used to...
Click to expand...
Click to collapse
WTH. Aroma is not a recovery, it is a filemanager "flashed" from and running within recovery. Absolutely no idea what are you talking about here. If you "flashed" Aroma, surely you have a working recovery, so flash a different recovery from your current one.
lolphirae said:
WTH. Aroma is not a recovery, it is a filemanager "flashed" from and running within recovery. Absolutely no idea what are you talking about here. If you "flashed" Aroma, surely you have a working recovery, so flash a different recovery from your current one.
Click to expand...
Click to collapse
I thought the same thing, but then I decided to leave that, I believe everybody knows what he means
Gesendet von meinem LG-P500 mit Tapatalk 2
;( ... oh no...!! i tried to flashed cwm recovery over AmonRa recovery using rom manager, and maybe this wasn't a good decision...
now i have latest cwm 5.0.2.7 but i think there is something seriously wrong.. when i boot into recovery, some weird things appear for 1-2 sec... moreover, while in recovery, my setting button became 'down' button, home button became 'up button' and search button became the 'ok' button...
i think something wrong is gonna happen with my optimus one.
u.bindal said:
moreover, while in recovery, my setting button became 'down' button, home button became 'up button' and search button became the 'ok' button...
i think something wrong is gonna happen with my optimus one.
Click to expand...
Click to collapse
Normal...and flash this http://forum.xda-developers.com/showthread.php?t=1779252 ...
deleted
u.bindal said:
;( ... oh no...!! i tried to flashed cwm recovery over aroma recovery using rom manager, and maybe this wasn't a good decision...
now i have latest cwm 5.0.2.7 but i think there is something seriously wrong.. when i boot into recovery, some weird things appear for 1-2 sec... moreover, while in recovery, my setting button became 'down' button, home button became 'up button' and search button became the 'ok' button...
i think something wrong is gonna happen with my optimus one.
Click to expand...
Click to collapse
Notonlyeyes said:
Normal...and flash this http://forum.xda-developers.com/showthread.php?t=1779252 ...
Click to expand...
Click to collapse
What do you mean by it's normal....??
Is it the same for all you guys having 5.0.2.7 reovery..??
u.bindal said:
What do you mean by it's normal....??
Is it the same for all you guys having 5.0.2.7 reovery..??
Click to expand...
Click to collapse
CWM 5.0.2.7. is buggy.
Use 5.0.2.0. / Amonra / New recovery CWM 6.0.0.1. port by Notonlyeyes
pmvyas said:
CWM 5.0.2.7. is buggy.
Use 5.0.2.0. / Amonra / New recovery CWM 6.0.0.1. port by Notonlyeyes
Click to expand...
Click to collapse
i know.. it sucks... it almost bricked my phone...!! it went to fastboot mode.. thnx a ton to the moderator of a xda thread which showed me the way...?
so is the buttons problem for all of you in 5.0.2.7...?
I had these problems. And so did many others as reported on XDA
Hi Folks,
I have a stock .587 firmware with locked BL.
I have done some tweaks on it listed below:
- New adreno libs.
- Walkman port V6 by ThilinaC
- removed bloatwares manually and freezed some others.
- JB SystemUI changes by ThilinaC
- adrenaline boost, etc.
I was learning on decompiling and recompiling the apk's. So I picked up the simplest one. i.e. enabling on screen buttons in framework-res.apk.
I made change into in one of the xml and I successfully rebuilt the apk. and flashed it using root explorer. But it gave bootloops.
I tried starting CWM recovery using volume down button at the Sony logo as usual. But it didnt start. I tried so many things like connecting to USB and restarting the phone at that time to start recovery by same pressing volume down button method.
But it didnt work still.
Since I was not able to go into recovery, and since my nand backup was some days old and had some data which was needed.
I flashed only system partition from the .587 ftf. using flashtool and rooted the phone again using normal procedure.
I thought the volume down button will work for recovery but it is still not working. (The button works normally when phone is on i.e for volume down process.)
Please help me what can be done.
P.S.: As of now I can go into recovery using x-parts or any other tool like titanium. But only manual recovery entry is not working.
So it means, I wont be able to go into recovery if I get bootloops again. And I am afraid to change/port anything on my phone now.
try the back button instead of the volume down button
gregbradley said:
try the back button instead of the volume down button
Click to expand...
Click to collapse
back button also didnt work.. Thanks for your reply anyways....
To add to my point....when I repeatedly press volume down/back button, the LED turns blue,,,but as per my observation, previously it used to stay till recovery starts, but now it turns on for 4-5 seconds and then goes off, and then the Experia bootanim shows up.
Is it like the exploit which activates recovery at boot time is damaged?(just a guess)..If maybe yes..how can I solve it?
Try to install recovery again via flashtool.
XperiaNeoVNoob said:
I tried starting CWM recovery using volume down button at the Sony logo as usual. But it didnt start.
Click to expand...
Click to collapse
XperiaNeoVNoob said:
back button also didnt work.. Thanks for your reply anyways....
Click to expand...
Click to collapse
How did you install CWM? Try taping on screen when you see boot logo.
gregbradley said:
Or flash a stock kernel with recovery included (I think you can still do that with locked bootloader, but not sure as I unlocked as soon as I got the phone)
Click to expand...
Click to collapse
Unfortunately you can't.
Madfysh said:
How did you install CWM? Try taping on screen when you see boot logo.
Click to expand...
Click to collapse
Thanks Madfysh...tapping on the screen worked... :good: so happy...
I had tried every button.. Didnt think of screen though...
Initially, I had installed CWM thru DoomLoRD's rooting toolkit. Then I had installed x-parts by pvyParts. There it said a new CWM version was available(v5.5). So I had upgraded that.
Was it the upgrade that had this change?
gregbradley said:
Try to install recovery again via flashtool.
Click to expand...
Click to collapse
Thanks Mate....Tapping on the screen worked. I dont think I need to install the recovery again. But thanks for your help... :good:
XperiaNeoVNoob said:
Thanks Madfysh...tapping on the screen worked... :good: so happy...
I had tried every button.. Didnt think of screen though...
Initially, I had installed CWM thru DoomLoRD's rooting toolkit. Then I had installed x-parts by pvyParts. There it said a new CWM version was available(v5.5). So I had upgraded that.
Was it the upgrade that had this change?
Click to expand...
Click to collapse
There is one version floating around which is using tapping on screen to enter in recovery, so since for you, back and volume- didn't work. Tap on screen was only option left, having in mind that you said that you can enter recovery using xparts, meaning that your recovery is installed ok.
p.s. I doubt you used doomlord's root toolkit to install CWM
Madfysh said:
There is one version floating around which is using tapping on screen to enter in recovery, so since for you, back and volume- didn't work. Tap on screen was only option left, having in mind that you said that you can enter recovery using xparts, meaning that your recovery is installed ok.
p.s. I doubt you used doomlord's root toolkit to install CWM
Click to expand...
Click to collapse
ok..got it..thanks...
For rooting I used Doomlord's toolkit. and the CWM 5.0 comes with that only..I had read somewhere about xparts...so installed it and updated the recovery.tar thru it...that must have done the trick...
Hi guys, I've got the European version of the Galaxy player 3.6, and I'm stuck on recovery: The home button doesn't work, and I believe it's because I flashed 4.2 kernel by mistake, when on android 2.3.6. I can't turn it on, because it loads up the recovery menu. I have tried to search for this issue but I haven't found an answer, so I posted it here, is there anything I can do or is this dead for good? Thanks in advance
Sparkles SP said:
Hi guys, I've got the European version of the Galaxy player 3.6, and I'm stuck on recovery: The home button doesn't work, and I believe it's because I flashed 4.2 kernel by mistake, when on android 2.3.6. I can't turn it on, because it loads up the recovery menu. I have tried to search for this issue but I haven't found an answer, so I posted it here, is there anything I can do or is this dead for good? Thanks in advance
Click to expand...
Click to collapse
Then reflash a 3.6 kernel on ODIN mode. The one by zaclimon.
kryptonify said:
Then reflash a 3.6 kernel on ODIN mode. The one by zaclimon.
Click to expand...
Click to collapse
I'm getting : "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and doesn't look like I can access the download mode.. I also went on to the kies but it won't recognize my device.. and I've got all the drivers installed
Sparkles SP said:
I'm getting : "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and doesn't look like I can access the download mode.. I also went on to the kies but it won't recognize my device.. and I've got all the drivers installed
Click to expand...
Click to collapse
Have you tried this solution by androthan http://forum.xda-developers.com/showthread.php?t=2308221?
kryptonify said:
Have you tried this solution by androthan http://forum.xda-developers.com/showthread.php?t=2308221?
Click to expand...
Click to collapse
Thanks, I will give this a try. I'll let you know how it goes
I can get to that first download menu, but everytime I try to press volume up, it sends me back to the Firmware upgrade screen..
Sparkles SP said:
I can get to that first download menu, but everytime I try to press volume up, it sends me back to the Firmware upgrade screen..
Click to expand...
Click to collapse
I never had this 'firmware upgrade' problem before. So im not really familiar to it. Where exactly is the firmware upgrade screen showing in the device or in odin?
kryptonify said:
I never had this 'firmware upgrade' problem before. So im not really familiar to it. Where exactly is the firmware upgrade screen showing in the device or in odin?
Click to expand...
Click to collapse
It's on the device.. Uhm it's basically something that appears whenever I turn on the phone, I can't access recovery or anything else, I can get to the part where it asks me to press vol up, but when I let go of the other buttons to press vol up it goes to the firmware screen, and I've tried almost everything, I tried not letting go, pressing volume first then letting go, trying to outspeed it, but it just won't work
Sparkles SP said:
It's on the device.. Uhm it's basically something that appears whenever I turn on the phone, I can't access recovery or anything else, I can get to the part where it asks me to press vol up, but when I let go of the other buttons to press vol up it goes to the firmware screen, and I've tried almost everything, I tried not letting go, pressing volume first then letting go, trying to outspeed it, but it just won't work
Click to expand...
Click to collapse
Hmm, I dont really know what else to add to this. Maybe try using adb to get to download mode.
And what exactly the kernel you try to flash? Can you link it?
kryptonify said:
Hmm, I dont really know what else to add to this. Maybe try using adb to get to download mode.
And what exactly the kernel you try to flash? Can you link it?
Click to expand...
Click to collapse
Yes, it was this one :
http://forum.xda-developers.com/showpost.php?p=39342399&postcount=1
at first the touchscreen didnt work, I don't really remember what I did after that and then just got stuck on recovery, now I cant even access recovery..
How do I use ADB?
EDIT, I flashed a stock rom with odin, but the kernel is probably still wrong, since I can't use the touchscreen.. but not stuck at that firmware thing anymore.. I'll try flash the kernel you recommended
EDIT 2: I can't flash it for some reason, it gets stuck at NAND Write Start!! any other kernels you can recommend?
Sparkles SP said:
Yes, it was this one :
http://forum.xda-developers.com/showpost.php?p=39342399&postcount=1
at first the touchscreen didnt work, I don't really remember what I did after that and then just got stuck on recovery, now I cant even access recovery..
How do I use ADB?
EDIT, I flashed a stock rom with odin, but the kernel is probably still wrong, since I can't use the touchscreen.. but not stuck at that firmware thing anymore.. I'll try flash the kernel you recommended
EDIT 2: I can't flash it for some reason, it gets stuck at NAND Write Start!! any other kernels you can recommend?
Click to expand...
Click to collapse
So, you can get to download mode? Then you shouldve flashed the kernel first. And then flash stock rom through recovery mode! You dont flash a rom with odin.
ok, so where is that NAND write start showing? if its on ODIN. use another odin version, try this one by androthan http://www.mediafire.com/download/82latn22s1kl7w2/andromint-Odin3-v1.85.zip
built especially for YP-GS1 eu.
Then flash stock kernel by zaclimon. Then boot to recovery and flash stock rom through recovery.
Heres another kernel http://forum.xda-developers.com/showthread.php?p=43190038#post43190038 but that kernel is just for that exact rom. And some other features not working. Check out the thread!
kryptonify said:
So, you can get to download mode? Then you shouldve flashed the kernel first. And then flash stock rom through recovery mode! You dont flash a rom with odin.
ok, so where is that NAND write start showing? if its on ODIN. use another odin version, try this one by androthan http://www.mediafire.com/download/82latn22s1kl7w2/andromint-Odin3-v1.85.zip
built especially for YP-GS1 eu.
Then flash stock kernel by zaclimon. Then boot to recovery and flash stock rom through recovery.
Heres another kernel http://forum.xda-developers.com/showthread.php?p=43190038#post43190038 but that kernel is just for that exact rom. And some other features not working. Check out the thread!
Click to expand...
Click to collapse
Thanks mate, I'll let you know how it goes!
EDIT: I'm flashing a lot of kernels now, trying to get one that works, but no luck, what would I have to do, step by step? I have a stock rom that I flashed with odin.. no touchscreen or buttons working (except for the power button)
Sparkles SP said:
Thanks mate, I'll let you know how it goes!
EDIT: I'm flashing a lot of kernels now, trying to get one that works, but no luck, what would I have to do, step by step? I have a stock rom that I flashed with odin.. no touchscreen or buttons working (except for the power button)
Click to expand...
Click to collapse
Open odin v1.85
Press PDA, select kernel, .tar file (this kernel by zaclimon http://forum.xda-developers.com/showthread.php?t=2198234 )
Power off device then go to download mode
Click start on Odin.
Now you should be able to boot to recovery.
Wipe cache, data, factory , dalvik
Download stock rom ( http://forum.xda-developers.com/devdb/project/dl/?id=7404 ) then copy to device
On recovery, select install zip from sdcard, select stock rom ^
Reboot.
kryptonify said:
Open odin v1.85
Press PDA, select kernel, .tar file (this kernel by zaclimon http://forum.xda-developers.com/showthread.php?t=2198234 )
Power off device then go to download mode
Click start on Odin.
Now you should be able to boot to recovery.
Wipe cache, data, factory , dalvik
Download stock rom ( http://forum.xda-developers.com/devdb/project/dl/?id=7404 ) then copy to device
On recovery, select install zip from sdcard, select stock rom ^
Reboot.
Click to expand...
Click to collapse
I flashed the kernel with odin, but after i got a screen saying samsung, with an error icon or something on the bottom.. and didn't go to recovery, it then booted into the rom I have.. is there a way to get into recovery on this device? I have tried a lot of common button combinations but no luck..
Sparkles SP said:
I flashed the kernel with odin, but after i got a screen saying samsung, with an error icon or something on the bottom.. and didn't go to recovery, it then booted into the rom I have.. is there a way to get into recovery on this device? I have tried a lot of common button combinations but no luck..
Click to expand...
Click to collapse
So your phone is unbricked now? Pressing Home + Volume up + Power button is the proper mode in booting to recovery mode. Or if you could access internet on the device, install some apps that let you boot to recovery mode (like the RebootManager). The error at the samsung boot logo is perfectly normal!
kryptonify said:
So your phone is unbricked now? Pressing Home + Volume up + Power button is the proper mode in booting to recovery mode. Or if you could access internet on the device, install some apps that let you boot to recovery mode (like the RebootManager). The error at the samsung boot logo is perfectly normal!
Click to expand...
Click to collapse
The touchscreen still doesnt work though.. I got to the recovery, but the home button doesn't work.. so I can't select wipe data, and I've also tried the power button which didn't work
Sparkles SP said:
The touchscreen still doesnt work though.. I got to the recovery, but the home button doesn't work.. so I can't select wipe data, and I've also tried the power button which didn't work
Click to expand...
Click to collapse
I think theres something wrong with the device itself not the software. Hardware buttons difficulties I suppose.
kryptonify said:
I think theres something wrong with the device itself not the software. Hardware buttons difficulties I suppose.
Click to expand...
Click to collapse
It worked before I messed up the 4.2 kernel.. so I don't think it can't be the hardware.. Also the power button works to boot into download mode and recovery..
Sparkles SP said:
It worked before I messed up the 4.2 kernel.. so I don't think it can't be the hardware.. Also the power button works to boot into download mode and recovery..
Click to expand...
Click to collapse
Hmm, interesting. Ill try to flash the 4.2 kernel on my own device, and Ill take a look myself. haha i got lots of free time
kryptonify said:
Hmm, interesting. Ill try to flash the 4.2 kernel on my own device, and Ill take a look myself. haha i got lots of free time
Click to expand...
Click to collapse
hahaha uhm, be careful though! I'm certain there's a way to fix it, but since we don't know it.. Would a restore of a back up fix the problem? (curiosity, since I can't even do that )
Hi guys, I really hope u can help me, cause i admit i did my share of research and got no solution
My N8010 was using GNABO 6.5 and Boeffla Kernel. While using it the other morning, the tablet suddenly rebooted and got stuck on the Galaxy Note screen. It stays on it a few seconds then reboot to the same screen in a loop.
I can access the recovery menu (CWM 6.0.3.6 ) but my options there are pretty limited, cant wipe and cant install zip files. At the botton of the recovery i have the following logs:
Warning: no file_contexts
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
I read somewhere that the problem should be solved if i could install a new recovery through Fastboot. Problem is fastboot cant find my device when on bootloader (but i can find it through ADB).
Using ADB sideload to install new recovery or new ROM gave me error on CWM.
Please, save my Tabye.
_Gandour_ said:
Hi guys, I really hope u can help me, cause i admit i did my share of research and got no solution
My N8010 was using GNABO 6.5 and Boeffla Kernel. While using it the other morning, the tablet suddenly rebooted and got stuck on the Galaxy Note screen. It stays on it a few seconds then reboot to the same screen in a loop.
I can access the recovery menu (CWM 6.0.3.6 ) but my options there are pretty limited, cant wipe and cant install zip files. At the botton of the recovery i have the following logs:
Warning: no file_contexts
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
I read somewhere that the problem should be solved if i could install a new recovery through Fastboot. Problem is fastboot cant find my device when on bootloader (but i can find it through ADB).
Using ADB sideload to install new recovery or new ROM gave me error on CWM.
Please, save my Tabye.
Click to expand...
Click to collapse
Samsung devices don't support fastboot instead they have something called download mode, which you can entered powering off the device and then pressing Volume Down button + Power Button simultaneously, after a couple seconds you'll see a warning screen at the warning screen press Volume Up and the device will be in download mode. Then you can use Odin to flash a new recovery, I would recommend checking out this guide on how to flash a recovery with Odin, and this thread for a recovery you could flash for your device model. Let me know if you still have questions.
shimp208 said:
Samsung devices don't support fastboot instead they have something called download mode, which you can entered powering off the device and then pressing Volume Down button + Power Button simultaneously, after a couple seconds you'll see a warning screen at the warning screen press Volume Up and the device will be in download mode. Then you can use Odin to flash a new recovery, I would recommend checking out this guide on how to flash a recovery with Odin, and this thread for a recovery you could flash for your device model. Let me know if you still have questions.
Click to expand...
Click to collapse
Hey Shimp, thanks for the answer.
Unfortunately I tried to flash both TWRP and Philz Touch and, besides going everything ok with odin, the recovery did not change. It is still CWM 6.0.3.6
any other advice?
_Gandour_ said:
Hey Shimp, thanks for the answer.
Unfortunately I tried to flash both TWRP and Philz Touch and, besides going everything ok with odin, the recovery did not change. It is still CWM 6.0.3.6
any other advice?
Click to expand...
Click to collapse
Did you rename the recovery image to recovery.img before your .tar it and then flashed it via Odin?
shimp208 said:
Did you rename the recovery image to recovery.img before your .tar it and then flashed it via Odin?
Click to expand...
Click to collapse
m
I just downloaded a .tar and flashed it. isnt that right?
_Gandour_ said:
m
I just downloaded a .tar and flashed it. isnt that right?
Click to expand...
Click to collapse
Usually that will work however I have ran into times where I had to make sure the recovery image was named recovery.img and then tar'ed that recovery myself and then flashed it through Odin.
shimp208 said:
Usually that will work however I have ran into times where I had to make sure the recovery image was named recovery.img and then tar'ed that recovery myself and then flashed it through Odin.
Click to expand...
Click to collapse
Did that. No success either. Still same recovery.
_Gandour_ said:
Did that. No success either. Still same recovery.
Click to expand...
Click to collapse
Sounds like it is time to restock with the original firmware and Odin and start over.
es0tericcha0s said:
Sounds like it is time to restock with the original firmware and Odin and start over.
Click to expand...
Click to collapse
Already did that. Nothing happened.
_Gandour_ said:
Already did that. Nothing happened.
Click to expand...
Click to collapse
Another thing you could try is just flashing the stock recovery through Odin, and then flashing the new recovery you want over that in Odin.
shimp208 said:
Another thing you could try is just flashing the stock recovery through Odin, and then flashing the new recovery you want over that in Odin.
Click to expand...
Click to collapse
Well.. i can try that, how can i get the stock recovery? Couldnt find it.
_Gandour_ said:
Well.. i can try that, how can i get the stock recovery? Couldnt find it.
Click to expand...
Click to collapse
Did you use the correct firmware? Did it pass successfully in Odin? Did you perform a factory reset after using Odin to install the original firmware?
Stock recovery can be found here:
http://forum.xda-developers.com/showthread.php?t=2102677
es0tericcha0s said:
Did you use the correct firmware? Did it pass successfully in Odin? Did you perform a factory reset after using Odin to install the original firmware?
Stock recovery can be found here:
http://forum.xda-developers.com/showthread.php?t=2102677
Click to expand...
Click to collapse
Used correct firmware. It did pass successfully through odin. Factory reset seems broken.
I will try the stock recovery.
No success with stock recovery.
So... No way to fix at all?
_Gandour_ said:
So... No way to fix at all?
Click to expand...
Click to collapse
To clarify even after flashing the full stock firmware, then flashing another recovery your still stuck on the recovery you were trying to replace correct?
shimp208 said:
To clarify even after flashing the full stock firmware, then flashing another recovery your still stuck on the recovery you were trying to replace correct?
Click to expand...
Click to collapse
Correct
_Gandour_ said:
Correct
Click to expand...
Click to collapse
What settings are you using in Odin when flashing the stock firmware package?
shimp208 said:
What settings are you using in Odin when flashing the stock firmware package?
Click to expand...
Click to collapse
Put tar md5 file on AP/PDA, leave F Reset Time and Auto Reboot checked.
UPDATE:
I sent the tablet to a local technician and hes gonna charge me U$150 to make a repair on the board and restore the system. Does it make sense to you guys? Should i accept the service?