Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts
I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh
Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.
Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
as many Users i also had problems with the "Sleep of Death", but till now i could restart it with long pressing the power button. After updating to 3.2.1 the SOD did not appear for a while but then it came back twice and now i cannot restart. Neither with long pressing power button nor with the combination power+volume. Battery was fully charged and i also tried it with charging cable.
Does anybody have an idea how?
Just get Asus to fix/replace it man.
Dont wait for the warranty to run out...
SOD is caused by the stock kernel. The only way to make sure it doesn't happen again is by flashing in custom kernel like clemsyn.
goodintentions said:
SOD is caused by the stock kernel. The only way to make sure it doesn't happen again is by flashing in custom kernel like clemsyn.
Click to expand...
Click to collapse
Yeah but I've seen reports of "Stock" TF doing this so there's no way for them to change kernels.
Like stated, send to Asus
baseballfanz said:
Yeah but I've seen reports of "Stock" TF doing this so there's no way for them to change kernels.
Like stated, send to Asus
Click to expand...
Click to collapse
Huh? Can you elaborate?
goodintentions said:
SOD is caused by the stock kernel. The only way to make sure it doesn't happen again is by flashing in custom kernel like clemsyn.
Click to expand...
Click to collapse
ok, but how can i is it possible to flash a custom rom without seeing display messages and changing usb-mode?
notmatched said:
ok, but how can i is it possible to flash a custom rom without seeing display messages and changing usb-mode?
Click to expand...
Click to collapse
What messages?
i never rooted or flashed a tablet pc but as i remember doing it on my former htc hd2 i have to start the bootloader, waiting for message that usb connection is established and so on.
so i'm wondering how i can flash the TF, especially since i cannot establish a connection. at least the asus pc suite does not find it.
forum.xda-developers.com/showthread.php?t=1185104
Not al rooting processes are the same. The thread I linked to have idiot proof instructions.
goodintentions said:
forum.xda-developers.com/showthread.php?t=1185104
Not al rooting processes are the same. The thread I linked to have idiot proof instructions.
Click to expand...
Click to collapse
after reading and following your linked instructions - thx for that - i now installed ASUS Sync, ADB Driver, APX Driver, Root Toolkit but i don't understand how i should activate ADB connection without using the UI on the TF....because of black screen.
No need. You should be in apx mode when you use the 7.1 version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootkit asks if the pad is in APX-mode, what i suspect because the hardware-manager shows a running "NVIDIA USB Boot-recovery Driver for mobile devices".
so i tried to make a backup only with rootkit but nothing apparently happens for more than 30 minutes. i only see what you can see in the attached screenshot. if a close CMD-window rootkit shows "Error! Could not load bootloader".
Hi there!
I bricked my p920 a week ago while trying to flash the ported 3D-ICS rom from xbsall. I don't really know what I did wrong, but somehow I destroyed my bootloader.
However, using the "p920 resurrection guide" (http://forum.xda-developers.com/showthread.php?t=1942836), I was able to boot my phone again and to restore my nandroid backup, so that I'm back to stock-GB now (rooted, CWM installed).
Everything works fine, except that my phone does not find any network and has no IMEI anymore (yes, I know, these two symptoms are connected )
I tried to recover my IMEI using this guide here (http://forum.xda-developers.com/showthread.php?t=1734330), but I always get stuck at point 9 of the instructions (trying to type in the original IMEI using Tutty).
So far, everything goes according to the guide. I connected Tutty with my phone using COM-port 3 (the only port available in Tutty) and when I type "AT" in Tutty, the expected "OK" comes as a response.
But when I try to type "at%imei", the only response I get is "ERROR" and no dummy-IMEI shows up.
By accident I also typed "atimei" one time, the response I got was "56000 56000 OK".
...later today I'll add a screenshot with my latest Tutty-session...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, what am I doing wrong? So far I tried all that with two different Win7(64bit) PCs and via a virtual PC running on WinXP (32bit). All drivers for my phone, Omap and Infineon are installed (Edit: at my last try yesterday, the Infineon-driver didn't seem to work. After starting CP-download mode my PC gave an error, stating it wasn't able to install drivers.)
I also tried to use Putty and Hyperterminal instead of Tutty, but with the exact same results.
Any ideas?
Bye
a noob with an O3D
I was in the same boat as you but i flashed v10k kdz file with lg b2capp and my Imei was restored.
Hope this helps
Sent from my LG-P920 using xda app-developers app
Yup..just flash kdz file and your problem will gone
Use This Tuts
Fixed it!
Good news!
I fixed my problem.
Thanks for your suggestions about flashing a kdz, but I fixed it another way, because I wasn't able to find a functional download link for any kdz-file. o,O
So here is my solution:
I think my problem was, that I backed up my system with my original nandroid-backup too early.
I repeated the whole "resurrection guide"-procedure and let the V21E stock OS installed, in this OS I had no problems fixing my IMEI using Tutty,
Afterwards I then just booted into CWM and flashed my nandroid-backup from before this whole s**t.
I thank all of you on this wonderful forum, special thanks to all the devs for their life-saving guides!
Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Major kudos to diego930 for such a nicely detailed description of his problem!
Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.
Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!
When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.
ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.
Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug with the production line of Nokia? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatter file based flashing ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since that's meant to help.
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Note: I cannot access the recovery page with the Android mascots chest open, only the screen posted in the reply below.
EDIT: Downloaded OST (Nokia's desktop flash editor), not much help as I can't seem to find the type of file its asking for. Seems like it could be a problem with a com port on the phone side seeing as I've mucked about with other cables/sockets.
Any help is so so appreciated right now :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Faraheim said:
Hi!
Long time iOS jailbreaker finally moving to Android here.
Just got a spare Nokia 3, brand new.
Updated it from 7.0 to 7.1, than updated to 7.1.1.
Already its stuck in recovery mode due to what seems like a bug? I've seen loose forums about this issue but all guides are either in Hindi or don't actually solve the issue. I just need to ask someone to help guide me through this, since I'm from iOS I'm not very aware about what flashing is, scatters ect. I downloaded the base 7.0 from Needrombd.com, also downloaded SmartPhoneFlash Tool since thats meant to help but I'm still super lost
I've connected the phone whilst its in fastboot mode, than put the scatter in and clicked download. Takes about 4-6 minutes than instantly hits 100% with a error (pic bellow)
Haven't had a proper phone now for half a week and I'm a little anxious and I just want someone to help me out. Can't wait to finally get into Android!
Any help is so so appreciated right now :victory:
Click to expand...
Click to collapse
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
redweaver said:
Whaat!!! Even with all my experience customising android phones, I haven't had the nerve to try flashing my nokia3 with flashtool. Does your phone still enter download mode? If so I recommend that you flash your phone with OST
You can get more information from this link:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Click to expand...
Click to collapse
https://imgur.com/sIsqZoo
This is the only thing accessible. Good suggestion though. Seems we have a mystery on our hands.