So, I'm trying to fix a phone for a friend of mine. I previously put CM10 on it (not sure which version at this point), and he recently started getting stuck in a bootloop. I tried wiping /data & /cache, didn't help. Tried re-installing the rom, didn't help. Tried installing the latest versions (both stable and nightly), didn't help. Tried installing arrgh's kernel, didn't help. Now I'm trying to get it back to stock, just to see if that'll work. I can get into fastboot just fine, and both cwm and skrilax's recovery work, but the only guide I found that has working DL links is this one: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9, and while I can get TWRP installed and boot into it, I'm unable to select anything. I don't know if the program is acting up or if there's an issue with the touchscreen, but it's really frustrating. I've got the .win files ready to go, but not being able to navigate TWRP is holding me back. Is there any other way to install these files, or is there a way to get TWRP to work? I'm using the latest version (2.6.3.0). Would installing an earlier version work? Is there any known way to fix the bootloop issue? Is there a rom more stable than the official CM10? I realize that's a lot of questions, but as I'm at the end of my rope here, I figured I might as well get it all out there, and hope someone can point me in the right direction. Thanks in advance for any help you can give me.
Ghinn said:
So, I'm trying to fix a phone for a friend of mine. I previously put CM10 on it (not sure which version at this point), and he recently started getting stuck in a bootloop. I tried wiping /data & /cache, didn't help. Tried re-installing the rom, didn't help. Tried installing the latest versions (both stable and nightly), didn't help. Tried installing arrgh's kernel, didn't help. Now I'm trying to get it back to stock, just to see if that'll work. I can get into fastboot just fine, and both cwm and skrilax's recovery work, but the only guide I found that has working DL links is this one: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9, and while I can get TWRP installed and boot into it, I'm unable to select anything. I don't know if the program is acting up or if there's an issue with the touchscreen, but it's really frustrating. I've got the .win files ready to go, but not being able to navigate TWRP is holding me back. Is there any other way to install these files, or is there a way to get TWRP to work? I'm using the latest version (2.6.3.0). Would installing an earlier version work? Is there any known way to fix the bootloop issue? Is there a rom more stable than the official CM10? I realize that's a lot of questions, but as I'm at the end of my rope here, I figured I might as well get it all out there, and hope someone can point me in the right direction. Thanks in advance for any help you can give me.
Click to expand...
Click to collapse
CM10 was never really "stable" on the Q. 10.1 is pretty solid, and 10.2 runs fairly well as well.
If you want to go back to stock, why not just use RSD lite?
http://forum.xda-developers.com/showthread.php?t=2095536
arrrghhh said:
CM10 was never really "stable" on the Q. 10.1 is pretty solid, and 10.2 runs fairly well as well.
If you want to go back to stock, why not just use RSD lite?
http://forum.xda-developers.com/showthread.php?t=2095536
Click to expand...
Click to collapse
I think it was 10.2 that I put on originally.
I would love to use RSD, but like I said, all the guides I found had dead DL links.
Ghinn said:
I think it was 10.2 that I put on originally.
I would love to use RSD, but like I said, all the guides I found had dead DL links.
Click to expand...
Click to collapse
Uhm, when you talk about working download links you link to some recovery hack.
I'm talking RSD Lite, and using fastboot to flash all of the stock stuff back.
Please read the link I sent - I can download those FXZ files no problem.
arrrghhh said:
Uhm, when you talk about working download links you link to some recovery hack.
I'm talking RSD Lite, and using fastboot to flash all of the stock stuff back.
Please read the link I sent - I can download those FXZ files no problem.
Click to expand...
Click to collapse
Huh. Must be late, totally didn't see that you had posted a link. I think I wound up on that page at one point, but the latest version of RSD Lite I could find from a site that didn't look sketchy was 5.7. When I search for 6.1.5, I get a lot of random download links (don't usually trust those, and a lot of non-English sites.
Yeah, may need to stop for the night and pick it back up tomorrow. Completely missed that there's a link to 6.0 on that thread. Will try that. Now, when you say to use RSD and then using fastboot to flash the stock stuff back, what do you mean? I thought RSD would take me back to stock.
Ghinn said:
Huh. Must be late, totally didn't see that you had posted a link. I think I wound up on that page at one point, but the latest version of RSD Lite I could find from a site that didn't look sketchy was 5.7. When I search for 6.1.5, I get a lot of random download links (don't usually trust those, and a lot of non-English sites.
Click to expand...
Click to collapse
I posted a direct link to 6.0 here, others posted their links in that thread as well.
Thanks for all your help. Will get RSD from that thread and try the files you linked. Hopefully that gets me further.
Yeah, RSD got me back to stock. The phone is borked anyway; the power button is iffy at best, and the touchscreen has stopped working, so he's gonna haveta try to get a replacement. Thanks for all the help.
Related
I think I'm posting to the right place. I have been playing around with the various mods, tnt lite, vegan, cyanogen, and somewhere along the way it got stuck to the point it is giving me an error right when I start the tablet saying "magic value mismatch". First time it happened I was able to get back to recovery. And I tried to restore, and didn't work. Tried clearing cache and it hung there for over thirty minutes. Now I can't even get into recovery and error reads the magic value mismatch. So am I bricked or is there a way out of this? And anyone try returning a bricked tablet to Sears? I'm still within my 30 day window.
Sent from my Droid using XDA App
Here's a nice link:
http://forum.xda-developers.com/showthread.php?t=860493
Thanks for the link. This seems to work, as I did not know the low level capabilities. Hopefully, I'll be mod'ing again soon! And for anyone in my position between these two links I figured it out where to get the files:
forum.tegratab.com/viewtopic.php?f=6&t=8
forum.tegratab.com/viewtopic.php?f=13&t=18&p=170
Did you use a newer version of clockworkmod (.12 or higher) with the device, and attempted a firmeware update? If so, it's a known issue and it's why I'm still using .8, right now.
It's not bricked, btw. This device is virtually unbrickable - you will probably need nvflash to fix it, and I have a post that can point you in the right direction:
http://forum.xda-developers.com/showthread.php?t=861950
Hope this helps!
Thanks, but I'm now getting the issue some others had in the other forums, but I don't see a fix where every boot ends up in APX mode. How do I get out of that?
As a side note, I did try the latest updated Clockwork recovery last night, which I believe is 2.5.1.8, that seemed like they added support from ROM Manager.
Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!
jkpatel79 said:
Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!
Click to expand...
Click to collapse
You might one of the newer devices with the swapped partitions (thats the 11/26 one you used). We still don't know why this is - very bizarre as to why VS (or whatever vendor they use) did this.
roebeet said:
This device is virtually unbrickable
Click to expand...
Click to collapse
Virtually is right. I accidentally bricked mine because I hit one of the devkit .bats while trying to reflash to stock
Yes, I'm a noob,to XDA, but I am pretty tech capable otherwise.
Yesterday, I unlocked the bootloader on my OneX, installed TWRP 2.3.x recovery, flashed CleanRom, ended up with a soft bricked the phone (still not sure what happened, but I think it was my stupid ancient work computer), tried to reinstall it, but the zip file was no longer in the SD card, tried to mount in recovery, but it was unsuccessful, tried to reinstall the 2.20 RUU, but it failed (all of these were probably B/C my work computer again). Gave up and came home. Got home to my modern PC, reformatted my SD, transferred Zips again and was finally able to get CleanROM to install correctly. All seems good, I setup the phone last night.
However, I have a problem with hyper-links that Scott has already acknowledged here:
http://forum.xda-developers.com/showpost.php?p=38936130&postcount=9922
I would have just asked this in that thread, but I don't have enough posts to write in Dev forums.
So, does anyone mind directing me to some basic instructions for 'flashing' the Link Fix Zip that Scott mentioned? I am assuming it is not the same method as installing the ROM.zip from TWRP, or is it?
After soft bricking yesterday, I'd really prefer some hand holding on this so that I don't mess up the successful CleanROM install.
Thanks in advance.
flash it in recovery just like the rom
jerrycoffman45 said:
flash it in recovery just like the rom
Click to expand...
Click to collapse
Thanks! That took all of 30 seconds plus reboot. Links working now.
Problem Solved.
Thanks Jerry!
please add solved and give thanks
DvineLord said:
please add solved and give thanks
Click to expand...
Click to collapse
Done, unless there is a tool for marking the thread "solved". I looked but didn't see anything.
NM, I figured out how to change the header.
Ok, I've done something stupid and I don't know what.
I've searched the forums for about 5 hours now, and can't find any help. If I've missed something, I apologize. I'm kind of frazzled.
I was trying to install an updated ROM from my internal SD via CWM recovery. There was an error, and now I'm stuck in recovery mode. I've tried clearing everything, but it won't boot to anything other than the CWM Recovery screen. I can't go into download mode to flash anything, or else I would just flashback to stock and start over. I even tried the whole taking your battery out and plugging the tab in to go to DL mode, but that does nothing.
We're dealing with a Galaxy Tab 2 7.0 P3113.
I'm about to cry.
Plz halp.
I might have it fixed now, but I don't want to get ahead of myself.
I finally managed to time my button mashing well enough that I'm in download mode. Will update soon.
If anyone cares.
I GOT IT
Ok, so I sill don't know what I did to end up in his mess, but through what I count as sheer luck I ended up in download mode, and was able to use ODIN to flash a stock rom.
I would delete this thread, but I want to leave it open in case anyone else runs into the same issues.
I had a similar issue when trying to update my rom, I found this to be particularly useful: http://forum.xda-developers.com/showthread.php?t=2302599
basdxz said:
I had a similar issue when trying to update my rom, I found this to be particularly useful: http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
I did read that, but I was flashing a GB ROM, so I figured it didn't apply. I do appreciate the tip, though.
Tried to root my phone that just came in the mail today. I am stuck at the mi screen.
Tried to download from official site but the download keeps failing.
A mirror to the new update so I can flash stock and any advice would be great!
Thanks all
Which version are you talking about?
Latest is 6.6.6.0 as far as i know.
The version with 6.6.8.0 is only for Asia and not released for the world.
About rooting: use the toolkit v4 (and not v3)
First install TWRP via that toolkit and only then start the root proces.
Worked for me, but if you do in another order, you will get stuck.
http://en.miui.com/thread-117336-1-1.html
Thanks for the reply and the quick guide to rooting it. I may have been trying it with something other than V4 which could have caused the stall at the "mi" screen.
I think I might just have to wait until their servers are back up because I'm pretty sure ill have to do the fastboot flashing method.
@gotmicah
I had problems downloading too the last days...slow speed and after a few MB it kept failing. In miui forum i found a tip about this tool http://www.freedownloadmanager.org/
Just copy the download link in there, worked great
And i think if you install twrp and flash your Rom, it should be enough.
Yeah, and one more thing. Xposed doesn't work in MIUI, but it does work on my build of CM12.1. Don't try using Xposed, caused a lot of problems for me (like apps disappearing etc) and don't use OTA. Download the update zip from the website and flash manually. Just thought I'd put this out there
rob rich said:
@gotmicah
I had problems downloading too the last days...slow speed and after a few MB it kept failing. In miui forum i found a tip about this tool freedownloadmanager
Just copy the download link in there, worked great
And i think if you install twrp and flash your Rom, it should be enough.
Click to expand...
Click to collapse
Thanks dude, you're the true MVP here! I used something similar to freedownloadmanager and was able to get the newest fastboot version in around 2 hours! Sounds slow, but better than a failed DL (I had to remove the link in the quote because im a new member)
Evil Tak said:
Yeah, and one more thing. Xposed doesn't work in MIUI, but it does work on my build of CM12.1. Don't try using Xposed, caused a lot of problems for me (like apps disappearing etc) and don't use OTA. Download the update zip from the website and flash manually. Just thought I'd put this out there
Click to expand...
Click to collapse
This is useful, thanks!
ALSO
I just want to let everyone know that may be searching because of a bad flash or similar situation...
If your flash keeps failing, switch computers and try again. My flash would only take a few seconds, say successful but the phone would be stuck in fastboot mode. I installed the same exact files/ drivers on another laptop, tried again and within a few minutes had a perfectly function phone again. Of course this was after hours of frustration and it ended up just being the computer I was flashing it on...
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.