I have messed with lucky patcher and google framework the android started acting strangely, I rebooted into recovery, wipe cache and data and the phone stuck on micromax, however I have upside down operatable CWM mode available and Instead flashing it with custom or stock rom I want to flash it with Ubantu Mobile instead. The official website Ubantu.com have no links to any OS of any king they are just promoting there device there. Can you guide me through the process, Thanks in advance:fingers-crossed:
Oh I backup the Rom original which on restoring from sd card give MD5 error tried deleting file inside no luck there
Related
PLEASE PLEASE HELP i tried unlocking and rooting my nexus s, but i epic failed... now i can only access the bootloader... so i accessed it... unlocked it.. then tried to flash the clockworkmod recovery.. it said OKAY but then just gets stuck at the google screen with an unlocked lock.. i can't even access my phone.. i can only access the bootloader and im freaking out please help !
I don't like 3.0.2.4 so download http://forum.xda-developers.com/showthread.php?t=988686 corresponding to your Nexus S model
rename it to recovery.img [assure that you have extensions shown otherwise it'll be recovery.img.img]
put it in /sdk/tools/
set your phone in bootloader mode
cd <wherever your SDK is>
fastboot flash recovery recovery.img
go into recovery
OH MY GOSH, KAY NOW I HAVE CLOCKWORK MOD but i can't access my internal SD card.. and it still won't fully boot.. again it just gets stuck at the google bootscreen.. but atleast i have clockwork mod.. so whats next ? :O
so i got clockwork recovery, and as soon as i get into it.. it gives me a bunch of errors about not being able to mount cache and find it and find the recovery.log (about 8 or 9 lines of code).. but the recovery still works.. and i found a stock zip from google search.. now i tried to flash it (by first mounting my storage.. then putting the zip on my storage).. then tryed to a restore from the recovery.. it checks MD5 sums.. then it gives me a lot more error codes... could you please help ?
Well, to begin with, you should specify your phone model and provider because each build needs different ROM. And you shouldn't flash any random ROM from google. Instead try to lookup for the correct stock ROM in the Nexus S Development forum.
well im with Rogers Wireless (From Canada) and my phone model is the GT-I9020 and the problem im pretty much getting now is that it can't find boot and cache partitions...
EDIT** i can access adb aswell now
Have you tried downloading and flashing a custom rom from the nexus s android development section? (CM7 for instance) You mentioned previously that you put a stock zip to your internal storage but ended up restoring instead? Try downloading a custom rom, mount USB drive, copy the rom to the sdcard, unmount USB drive, wipe factory, wipe cache, advanced>wipe dalvik, choose zip to install, install the custom rom. Ideally that should get you past the Google logo and into a working build.
Sent from my Nexus S using XDA App
the thing is.. it can't even restore the original zip.. like the partitions can't be found.. and it seems like its a brick now plus the phone isnt rooted... i was trying to root it.. then this whole thing came up...
When you say restoring from original zip, are you talking about a nandroid backup? Or a stock rom you downloaded? In any case, I would still recommend doing what I mentioned earlier. And no, your phone is not bricked at all.
Sent from my Nexus S using XDA App
it's a nandroid backup ( i took the img. bundle in the folder thats labeled with the date *ie. 2010-12-22.21.06.07*).. i tried installing this as a backup.. and it wouldn;t work.. i got *checking md5 sum.. then 6 or 7 lines of code all seeming to relate to not being able to mount the cache partition and not being able to find recovery.log in the /cache... so i think my cache-ext is screwed up.. I tried using the sdpart script in adb.. and it didnt help matters... so im not sure what to do now
The Problem:
When I select Clockwork Recovery Mod from the three button process, the phone reboots and the entire system gets a factory data reset.
What did I do wrong?
My mobile is rooted and running a Jelly Bean Rom. I did a Factory Data Reset from the system i.e. from within android not from Clockworkmod recovery menu and since then this problem has occured. It appears that factory data reset command is stuck somewhere in the boot.
Current Condition:
The Mobile is running perfectly fine without any problems. I can reboot and turn off the phone and it will load Android Jelly Bean Rom smoothly. The problem only happens when I try to access Clockworkmod recovery.
Solutions tried so far
I tried to reflash Clockworkmod image update from Mobile Uncle MKT tools, it rebooted the mobile and did a factory data reset of the system. The same thing happens no matter how many times I try.
I couldn't reflash Clockworkmod using rom manager as it does not recognize by device.
Was it working fine before?
Yes Clockworkmod was working absolutely perfect. I installed various roms from it and did backup of stock rom and even twice restored the stock rom.
Phone Specifications:
It is a local variant of a phone found in Germany going by the name of Mobistel Cynus T2 and as Micromax A110 Canvas 2 in India.
Would greatly appreciate any help.
You will be OK
Not psychic, but I think you loaded an incompatable version of CWM and then flashed, a buddy of mine just went through this, he didn't pay close enough attention or maybe its just some weird stuff in the universe-HA!
Ok, you are probably in recurring boot cycle, if you can get phone into boot mode, you know the combination of keys to be able to flash something!
Get to your computer and find the original OS that it came with out of the box, it will be a large download, it could be anywhere from 480 meg to darn near a gig.
Go get Odin 3.07 is the latest I think, anyway use Odin to flash the original OS. Start from out of the box fresh. It wouldn't hurt to stop by the play store after set up and get Triangle Away, it gets rid of the counter that is tripped when a custom rom is flashed.
Good Luck.
Fixed
1). Download the Stock Recovery Rom and CWM recovery Rom for Qmobile Noir A10 from here.
2). Download Mobile Uncle Tool from Play Store.
3). Rename the Stock Recovery Rom to "Recovery.img" and place it on the root of the SD Storage.
4). Open Mobile Uncle, grant it super user access and from its menu select Recovery Update.
5). Then select the Recovery.img (mentioned under the SD Card header), after which Mobile Uncle tool will prompt for a "Reboot in Recovery Mode" to which yes should be selected. If you have accidently selected "no" then you can select Reboot in Recovery from the main menu of the tool.
6). After the Reboot the mobile may not enter into Stock Recovery Mode and instead perform a Factory Data Erase of the android system so don't panic and repeat steps from 2-5. It happened with me therefore I am mentioning it here.
7). After you have successfully entered the stock recovery mode, reboot you mobile phone and let it load the Android Operating System.
8). Now rename the CWM Recovery Rom to "Recovery.img" and using it replace Stock Recovery Rom, mentioned in step 3, on the mobile's SD Card.
9). Open Mobile Uncle Tool again and repeat step no.5.
10). Upon reboot, your phone will be in CWM recovery mode.
Now do the robot dance and look like an idiot.
I am flashing OmniROM-4.4.2 for my Huawei Ascend P1 using Philz Touch Recovery based on cwm 6.0.3.7.. I did it successfully once, created a backup and got back to my old liquidsmooth rom by Spanorg so that I could do a proper backup of my files to transfer it to the new rom. However, upon wiping everything, now everytime I try to flash the OmniROM-4.4.2, it says 'set_perm some changes failed status 7 installation aborted'.. I have the backups, but it says they have md5 checksum mismatched.. and when i try to go into my old rom, it gets stuck in the boot loop..
I have tried clean installing a couple of times, but nothing seems to work..
Any fixes, guys?
hi folks,
My device was on cm11 and I wanted to try the slim6 rom and the new TWRP update for the recovery. I tried the TRWP unified version of Andi but after the flash succeded , everything from the tablet (Rom, data, system, etc..) was completly erased. Now the new recovery dosent read anything, even if I put a SD card with the files to flash. I tried to flash a another recovery with odin but the odin program freeze when I select the recovery . I can't find any working links for stock firmware and the one from sammobile crash most of the time before the end.
Any ideas of what happened on my device ?
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.