My phone is a Motorola Milestone A853.
I was testing out the new CM9 mod by kabaldan when I found myself running into a huge screw-up. No, not one that I believe is not reparable. Just one that is hard to get out of. Let me explain:
Having a wi-fi problem on multiple versions of the CM9 alpha ROM for the Milestone, I found myself trying to debug the situation in many ways. i.e. reflashing the ROM, wiping data/caches repeatedly... and trying a purported fix in the CM7 thread that did not work. In the middle of things, I decide do to format my SD card.
Bad idea.
Since the SD card pretty much contains OpenRecovery among other things it got wiped. Now I pretty much cannot access my recovery (which is Androidiani OpenRecovery).
I actually had the OpenRecovery folder backed up onto my hard drive, but copying it back has resolved nothing. It gets to that icon, stays there for a second, then fails and reboots back into the main OS.
This has happened to me before during about when I just got into modding the phone ROM (recovery screw up), which I recovered from using RSDLite to reflash a recovery. But now RSDLite does not even recognize my phone - this may have to do with the fact that it's running the CM9 ICS alpha ROM. So I can't repair the recovery, and I can't get my phone back to where it previously was and solve the wi-fi problem.
Thank goodness this has happened on a free long weekend. My phone is actually okay to use when I turn it on(can make calls, messages) but has none of my apps and whatever on it and I cannot fix anything with recovery, so on-the-go usage is near-useless. At the least I have a backup (Novo 8 tablet) for on-the-go stuff. But I want to get my phone back right away.
I know that there is another way to do this (sbf_flash I believe). I have access to a laptop running Xubuntu Linux (my old laptop, which was replaced by my tablet) to use sbf_flash, but is it possible to use it from Windows? (I think so).
Thanks to anyone that can help. I've done a lot of searching so far but I haven't found a huge amount plus I want to focus on getting this done and fixed sooner. I'm looking forward to full-fledged use of ICS on my Droid; from my experience so far, it's much faster than what I have moved from (latest version of MIUI).
What os do you have now?
You've been flashing stock roms. This restores stock recovery. Hence the need to flash vulnerable recovery or OpenRecovery will not work.
Along with OpenRecovery folder you need update.zip file.
Try to reinstall drivers since RSDLite shouldn't care what OS is on the device. Maybe it'll solve pc->device conectivity.
RSD won't detect device unless in bootloader mode.
If recovery won't boot automatically press volume up + camera.
Everything you might need is on this thread! Look for it.
1) "My phone is a Motorola Milestone A853"
2) "I'm looking forward to full-fledged use of ICS on my Droid"
The second is a pet talk I guess?
I thought RSD required that Phone portal USB connection option through the phone be working for recognition. Nothing happens in bootloader mode, pretty much. But I'll look into it. If RSD really shouldn't care about the OS on the device then I def have some driver reinstalling to do; is that true?
Current OS installed is the CM9.0 (ICS Android 4.0.3) alpha by kabaldan.
Same occurs when doing volume up + camera. Loads for a second, then quits (i.e. files not present, cannot complete loading).
You use RSDLite to flash .sbf files. That works only in bootloader mode.
When in bootloader mode and when you plug in usb cable the device should respond with something like USB OK, don't remember anymore, as should rsd give some info that the device is connected (left and right parts of main window provide info about device and the sbf file, respectively).
RSD finishes, phone boots, you reboot in bootloader, flash vulnerable recovery, prevent booting to OS and instead boot to recovery (OpenRecovery by now) by pressing hw keyboard X, verifiy that /system/etc/install-recovery.sh does not exist but if there delete it! or system will restore stock recovery.
More detailed instructions can be found on this forum and this thread.
Prior doing any of above: verify that you have openrecovery folder and corresponding update.zip in the root of your sdcard. Then try to boot to OpenRecovery as it seems to me that your main (or only) problem is that recovery on sdcard is broken.
or get another sdcard with recovery on it,insert on your phone and tadaa
Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!
xd_1771 said:
Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!
Click to expand...
Click to collapse
Just to prevent anyone else from having the same problem, I'm going to point out this:
update.zip from any of the recovery packages is needed every time you boot into recovery. It's a "special" update that is designed to crash the bootloader's update function and run unsigned code, such as a 3rd party recovery. Nothing ever actually gets flashed when this update is run.
Without the update.zip, you have no way to tell your device to launch the custom recovery, as we can not flash a replacement directly to the phone's memory because of Motorola's stupid signed-code-only checks.
Related
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
frankkienl said:
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
Click to expand...
Click to collapse
It's not bricked. It's really hard (but not impossible) to brick a Xoom. They are hardy beasts.
I do wish you hadn't tried the revert/relock thing. You just made it worse as you tried to flash a 3G image on a WiFi only device.
But don't worry, it is possible to come back from this.
Just so you know, your first mistake was using old guides (though filled with good info, but files are not necessarity right) and mixing the sources. There are much newer guides in the Development section (page 1) for non-US Xoom, and I think people have better result when they stick with one source (in this case xda Xoom forum).
Second mistake is that you used the wrong recovery image...you used the v4.0.0.4 from RomManager, which is not compatible with the external micro sd card. You need the v3.2.0.0 R4c (Tiamat version). That's still the best most current version for the Xoom.
http://forum.xda-developers.com/showthread.php?t=1074979
If you had not gotten impatient and tried to revert/relock, you could have just flashed the proper recovery image and you would be good to go.
Good luck!
You seem to know your way around adb and fastboot so I'm sure you will be able to recover. Find the proper stock images for your Euro WiFi Xoom and flash them, download and flash the correct recovery image and you can take it from there.
It works again !
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
frankkienl said:
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
Click to expand...
Click to collapse
Excellent! So glad to hear it. You have skills so I'm sure you will be coool from now on.
just an update
This is an old thread so I'm putting this here for google searchers, like me.
I had the same problem but here's what extra I found/noticed
(1) To restart the xoom when it's in this state hit power button and volume up
(2) You can see that the tablet is still responsive if you hit volume down after 2 seconds as you'll get some options
(3) For me it wouldn't work if I used the motorola cable (yes, the real one) in the front pc usb ports. I had to use the usb 3 ports at the back of my pc. Yes, it's that picky! The difference was when I used fastboot to install the system image. It took 3 minutes then gave up, stuck the cable in the back of the pc instead and it took about 10 seconds and worked first go!
(4) The pc didn't recognise the xoom and adb didn't work, i.e. it said no device attached. However fastboot did recognise it
After point (4) I realised it wasn't bricked and could move forward
thanks to the other posters here for making me realise there was hope
Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.
first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2
dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.
You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.
Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!
I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus
I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro
ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.
i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?
Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.
some notes
rooted using Root RK29 Tab Toolkit 1.3.
reset and vol + = flash mode rock usb.
RKAndroidToolv1.37 and RKBatchToolv1.7 work for flashing.
used rock usb driver included in either of the flash
tools. when flashing several things needed done to
enable flashing and or adb. do not enable usb storage
on the device. on windows pc used the safely remove
mass storage tool. only on the removable drives that
showed in my computer after plugging in the tablet.
in RKAndroidTool or RKBatchTool use the "switch" button
to put the unit into flash mode. I used RKAndroidTool
to flash the cwm. I tried several cwms, PER5274B_CWM.zip
was only one to boot to recovery for me
(tried many including ones from developerof cwm, just
happened to find one to boot after trying
over and over). so far. succesfully made full backups of
the unit to sd card. obviously mount the ext sd in cwm
first before backing up to sd. succesfully flashed
gapps-jb-20121011-signed.zip using PER5274B_CWM.
the stock recovery tool rejected all gapps. note gapps
sometimes closes for no apperent reason with no error.
all other gapps versions i tried crash soon as i
opened them.
cwm file working so far PER5274B_CWM.zip. have only figured
out how to boot to recovery using reboot apk.
key combo is unknown to me so far. actively trying other cwms.
Other cwm's have booted to a white screen for me.
a word to the wise, make full flash backup soon as you
get cwm on. its the only way to turn back to stock as
far as i know. I cannot find a factory rom for this
unit anywhere.
downloading cm 10.1 for rk29xxboard now, will report
results!
Cheers hope this helps out someone.
well cm10 didnt work out so well. the unit is now resting with no response. I can however still flash it with rkandroidtool. the issue I am facing now is I do not have a full dump image for this unit. I am looking for one that will at least allow me to get it to boot properly to cwm lol. I can see it with rkbatchtool as well. what I would need there is the proper parameter file. pretty sure thats all I need. I did happen to make a backup with cwm but if I cant get the tablet into cwm (currently a no go) thats not going to help me. figures I have since found out how to generate a parameter file.
good news is its not dead, just not working.
I have gotten my moneys worth out of it, not only in using this tablet but also in hacking the thing passing time.
will report further updates.
Cheers!
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
stinkster said:
Well its running again, after many firmwares etc. I have the stock firmware running and two others I have modded removing system Apks I didn't want and adding a few as well.
Have several cwm backups as well, a few I plan to post links to. Googleplay works to, root, cwm and busybox also.
Still trying to get hardware keys working to launch cwm at boot by editing the parameter file. It will run when I edit the file with notepad++ and flash it but then I end up in a cwm boot loop forcing me to reflash the orig parameter file to get out of it. Cold boot will get me out if I completely drain the battery otherwise nothing short of flashing it will get me out of cwm. Using notepad++ and inserting "COMBINATION_KEY: 0,6,A,7,0" right after the kernel IMG line gets the power + volume key to start cwm at boot. Then I can't get back out lol.
Click to expand...
Click to collapse
Stinkster,
Have you made any other progress? Got my kids couple LT7035-F tablets.
Thanks
To the both of you... LT7035-J
curtisint has firmware for model lt7035-j; however, when using rkbatchtool it fails at 97%. My tab is only able to connect to the pc as of now. I can see it with batchtool; however, have not found a firmware.img file to flash to it that completes and works. Very interested in the parameters file you speak of in your second post. Don't know what you know now but I was able to get it root with a tool I found on the net. I think I have it somewhere. Well anyway I was trying to reflash stock firmware because I had no sound just a popping noise/key tone which was silent only when mute. If anyone could help out with a firmware.img that will work for me that would be great.
stink you sound like you know what you are talking about, do u java develop or something?