Related
I think i bricked my phone by fallowing this tutorial.
http://forum.xda-developers.com/showpost.php?p=3874647&postcount=406
It happened after flashing the spl.
My phone will not go past the white "t-mobile g1" splash screen.
thank you for reading.
Damn, another brick? Did you make sure you had a PVT board and not the DVT-1, DVT-2 boards? It's a known problem with the Special SPL that it pretty much bricks DVT board phones...at least so far. (check by booting with camera+power if possible, board type is shown on the first line of text)
Can you boot using home+power? Are you just stuck at the Splash screen? If so, after about 10 mins the screen will change, giving you an triangle error symbol. At this point push Alt+L. This should give you the recovery utility, where you will have access to wipe (you should prob do one) and reflash a rom.
Of course this is all assuming you have root already.
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
aronissleeping said:
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
Click to expand...
Click to collapse
Ok, so what you need to do is this:
1. Wait for the error message //remember it sometimes takes 10 mins or so
2. open keyboard, hit Alt+L //this will toggle your phone to the recovery utility
3. If you have root, you may have a recovery utility that says "JF version 1.43", if not you have the stock recovery utility
4. If you have root, you could try to DL pretty much any rom although I might try the Ion rom for its stability and simplicity //there are tons of instructions for flashing a new rom
5. If no root, search in the Dev section of the Dream forum for an OTA ( Over The Air, ie. stock) rom. In particular, search for Dreaimg.nbh, and read the instructions for reflashing it. This will help you gain root.
6. reboot, and enjoy (hopefully)
If none of that works, you can find the "Bricked G1's" thread on the Dev section too. I think your prob out of luck, but it's possible someone has/or is coming close to a fix.
re flashing ill let you know the out come
lol you didnt brick it since u can access the recovery image.
anyways what happened to me yesterday, i flashed latest radio, the latest spl and it wouldnt boot. i flashed a new system image but still no boot (t-mobile screen). I wiped the system (data partition) from recovery boot, and reflashed with a new system image, worked ok... so from what i get, u need to wipe / reflash system, if you upgrade spl...
is by using a card reader on a pc the only way to flash a different img if this happens to you?
my phone is in root and i'm on the same g1 screen. if i take the battery out i can boot to recovery mode but my only options are alt-w and alt-s. i've tried wiping and reflashing with the same spl img and it's not resolving anything.
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
Unofficial Cyanogenmod 10 (Jellybean 4.1.2) for Ouya - Experimental
**MUST READ**
Until Ouya releases a proper method to force the device into a recovery state this is considered risky. If you're ever writing to the boot partition and the power goes out, or you flash a bad kernel, your Ouya could quickly become a shiny new brick.
Because of this, the flashable zip I posted does not contain the boot.img. The boot.img is a separate download which you should use fastboot to boot. I recommend using 'fastboot boot boot.img' until this issue is addressed. Of course this means that every time you reboot your device you will have to force it to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img' (very annoying).
You can use 'fastboot flash boot boot.img' if you want to write the boot.img permanently, but YOU'VE BEEN WARNED. I am in no way responsible for anything that happens to your device.
Right after you install, go into settings and enable adb and adb root access, THIS IS CRUCIAL. You could be locking yourself out if you don't. If you forgot to do this and you find yourself stuck in a bootloop read the section titled 'Stuck in a bootloop' below.
Tested working
Wifi
Bluetooth
Audio
HDMI
Google Play store (Use gapps-jb-20121011-signed.zip)
Ouya Controller
Ethernet (Have to use 'netcfg eth0 up', 'netcfg eth0 dhcp' commands since we have no settings menu)
Expect bugs and please report them. I have not tested this thoroughly.
Make sure you take a backup of your stock Ouya using CWM.
Downloads
cm-10-20130702-UNOFFICIAL-ouya_1_1.zip
0ff08b8c5aaa85e6d091e4e079cdc79c
20130702-boot.img
60b4c4d82dbe317cd14a5deda09b0831
Tips
Disable Battery Icon
- Go to Settings > System > Status Bar > Battery Status Style > Hidden
Disable extra notification drawer items
- Go to Settings > System > Notification drawer > uncheck Airplane mode and Orientation
Set governor to Performance
- Go to Settings > Performance > Processor > CPU governor > PERFORMANCE (check 'Set on boot' to keep changes on reboot)
Stuck in a bootloop
If you ever get in a situation where adb is disabled and you forgot to boot the proper boot.img you might get stuck in a bootloop.
The only option is to try the following to force the ouya to reboot into recovery.
- Power off the ouya.
- Plug in a usb keyboard that has a sysrq or printscreen key
- Power on the ouya, right after the boot animation starts press the sysrq/printscreen + alt + i keys and hold for a second
- Wait a second and press the key combo again, sysrq/printscreen + alt + i, hold for a second
- Repeat this until the device reboots (You should see the boot animation freeze after a few times, this means your getting close :silly
- You should end up back in CWM with adb working
Changelog
7/2/2013
- First release
Source
http://github.com/khanning - Device tree
http://github.com/ouya - Kernel source
Thank you
Cyanogenmod Team and all contributers
Everyone here that started the discussion before I got my ouya. Reading through the threads helped point me in the right direction.
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
zanderman112 said:
So interested in trying this, but seems a bit unsafe atm. I'm going to be keeping a watch though, because I bought my Ouya knowing it'd be open to ROMS/etc. I bought it to be a cheap PC for my tv, and the default software doesn't really allow for that.
Click to expand...
Click to collapse
Same here. I'll wait for someone braver than me to jump in first. Water looks warm, though!
Sent from my SAMSUNG-SGH-I727
Devs, I propose the following to get rid of the potential brick risk:
Since we can't get into recovery manually (via HW buttons), let's reverse the role of SOS (recovery) and LNX (kernel). Since LNX is the booting kernel partition, let's flash recovery there and flash the kernel to the recovery partition. I believe we could do this by modifying the fstab and having our updater-scripts flash to the appropriate partitions.
From a cold start, a user will enter recovery (a minor inconvenience for safety). Depending on how we modify the recovery.fstab, getting to the ROM could be as simple as pressing power twice (recovery does a reboot system now and its fstab has the system actually reboot to the recovery partition, which is the ROM's kernel).
Definitely not straightforward, but should prevent bricks. Thoughts?
Sent from my Nexus 7 using xda premium
mybook4 said:
let's reverse the role of SOS (recovery) and LNX (kernel).
Click to expand...
Click to collapse
It sounds almost to simple to work! lol
Really though, I see no reason why this would not work... even without hardware buttons, its just selecting "reboot recovery" from the cwm menu.
Might need a discussion around how this would effect the sysrq+i recovery... I believe we would be safe as (from what i can tell) it doesn't boot to the SOS mmcblk directly, it just go's to whatever "recovery" is.
I already have my second ouya on the way so I have no issues testing it out.
I think it would be easiest for ouya corp to give us the boot loader source code and let us add I'll those features in ourselves
This is awesome. Maybe you should add a link to this on the OUYA subreddit. Hopefully more exposure makes it more obvious to OUYA how much we need easy access to recovery.
And if more exposure means more noobs bricking their console, then they'll all be contacting OUYA to fix it (since it's not explicitly excluded from the warranty), and that might get them on the ball to release stuff faster.
This should be fine. One of the things people may not know is that the Ouya is basically an "always on" device which is generally rarely shut down, so a cold boot is not a frequent thing. As a result, making a cold boot slightly less convenient isn't a real issue IMO, particularly as this will ONLY effect users who have opted to flash CWM and ROMs and stuff on their Ouya.
However, making such an extensive modification would mean we better be damn sure the OTA updates are prevented. I can easily imagine an OTA update coming along and breaking everything when it fails to properly update the device upon encountering the non-standard layout. Its one of those "that shouldn't happen" scenarios, but why chance it if we don't have to?
I am not too active on these parts anymore but wanted to post thank you for this and once they got proper recovery in place incase I bif my only media box I have for my tv I will give this a go!. ty again for all the work you have done.
This is what eventually will be on my OUYA, probably a dual boot. The reason being that a lot of games on the play store nowadays have controller support. So I can have a huge catalog of games through there. Also, not to forget movies, music etc.
And whenever I wish to play OUYA exclusive games I could hop back on to the OUYA Rom.
Best of both worlds.
Great work devs.
So, if I were to install this, permanently, the instructions would be as follows?
Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?
Sent from my SPH-L710 using Tapatalk 2
zanderman112 said:
Boot into recovery using 'adb reboot recovery'
Flash zip
Reboot to the bootloader using 'adb reboot bootloader'
Use 'fastboot flash boot boot.img' to flash the boot.img permanently.
Reboot, done?
Click to expand...
Click to collapse
The OP suggests that you don't do that quite yet, rather just boot into recovery, flash the zip, and use fastboot to boot the proper boot.img every time... This was you should always have the stock kernel installed on the /boot partition, and there are ways to get back to the recovery if you mess something up. So use 'fastboot boot boot.img' instead. If the kernel can't boot for some reason, currently you can use alt-sysrq-i to get back to recovery, if you mess up the boot partition, you can't, and you'll be completely bricked.
I hate to be the one to ask this, but could someone provide step-by-step instructions? I haven't had a reason to use ADB very much but I would very much like to enjoy my Play Store games that have already been purchased on my Ouya. Thanks in advance for anyone willing to take the time to explain this process a little better. :good:
Also, should we wipe anything?
Is CM10.1 on the horizon at all? What wouldn't work?
Good work man, oh so tempted but my kids use this for watching vids and so will keep my fingers crossed you find a way to make this more permanent. Keep up the good work
Sent from my GT-I9100 using xda premium
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
BUS DR1V3R said:
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
Click to expand...
Click to collapse
are you in fastboot?
super jay said:
are you in fastboot?
Click to expand...
Click to collapse
I am not entirely sure. The OP says to reboot to the bootloader using 'adb reboot bootloader' and then 'fastboot boot boot.img'. This is what I was trying to do, and I found that if I leave the spinning logo up long enough I can reboot bootloader, but when I try to fastboot the boot.img it just says <Waiting on device>.
BUS DR1V3R said:
Stuck at spinning CyanogenMod logo. Tried "adb reboot bootloader" only to get a "device not found" message. I do have the drivers and SDK setup and can use "adb reboot recovery" just fine.
Can anyone tell me what I'm doing wrong? All I have done is install the zip and wiped cache/dalvik. Flashing ROMs isn't something I do very often, but couldn't pass on getting my Play Store games on this device.
Click to expand...
Click to collapse
I'm running it right now with really no issues. What I did was reboot to recovery did a factory reset then formatted system, data and cache. Then installed cm10 and then rebooted to bootloader and flashed the boot.img and did a reset. After that I made it into system and looked around all happy then did a reboot recovery and flashed gapps.
Edit: didn't read closely enough sorry
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
If you could tell us more clearly about what did you do actually and which instructions did you followed?
DNA_Uncut said:
If you could tell us more clearly about what did you do actually and which instructions did you followed?
Click to expand...
Click to collapse
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
t-rayms said:
i followed(or tried to) the instructions from the site of androidmtk with topic
"how to root android one devices easily"
sorry but system will not let me paste the actual link.
Process involved the use of android one toolkit.
and now my phone no longer boots. Stuck with those 4 animated circles. I have to remove the battery to get out of that screen. But no matter what i did, isn't there a way to just install android? Like installing windows on a blank hard drive? Start from scratch? Loss of data is not a factor
Click to expand...
Click to collapse
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
t-rayms said:
After having issues with the low 4GB memory of the myphone uno, i decided to try rooting the phone using some online instructions using Android One Toolkit. I ended up bricking it. Now when i turn on the phone, its stuck with the 4 animated circles.
I am a noob when it comes to android phones, but i do know how to install windows xp, vista, 7. I have used online instructions to clone my pc HD using clonezilla. I believe that if someone were kind enough to give step by step instructions on what files to download(like the original "OS" / "image") and where to get them. And how to use the software, i can get my myphone uno back to working order. So please anyone out there, can you help?
Click to expand...
Click to collapse
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
devil anand said:
You don't need to go back on kitkat as DNA uncut says .....your device is running on which recovery ??
Click to expand...
Click to collapse
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
t-rayms said:
im sorry but i dont know what "recovery" is. The phone is also no longer turning on so i cant get that info. But im ok with trying kitkat and if the flashing of the ROM works, at least ill have a working phone. And go from there and experiment some more to get the most out of the device.
Click to expand...
Click to collapse
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
DNA_Uncut said:
Just follow the thread
http://forum.xda-developers.com/dream-uno/development/stock-rom-spice-dream-uno-mi498-t2915844
Download ROM (from the same thread)
http://forum.xda-developers.com/showpost.php?p=61588267&postcount=23
You should get back to stock kitkat (if you follow the instructions as explained). Once you get back your phone to working. Install ota updates you receive that will get you to stock 6.01
Click to expand...
Click to collapse
i installed the Android CDC Driver. DL the SP Flash Tool and the custom ROM. Rebooted the PC. Ran the SP Flash Tool. The final stage where i click on DL and connect my phone, nothing happens. The scrolling progress bar at the bottom of the flash tool doesnt start. With or w/o batteries in the phone. What do i do next?
devil anand said:
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
---------- Post added at 03:58 AM ---------- Previous post was at 03:49 AM ----------
When your phone is switched off. ....press the power and volume+ button at the same time and hold it till you see a menu .....then navigate to recovery as the menu instructs ....then tell me what you see
Click to expand...
Click to collapse
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
t-rayms said:
when i selected the recovery option, the next screen is a picture of the android robot lying face up. With its body panel door open with red triangle with black exclamation markm, "No command" prompt
Click to expand...
Click to collapse
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Link - kernel- http://www.thunderzap.in/downloads/
SuperSU - https://download.chainfire.eu/741/SuperSU?_e_pi_=7,PAGE_ID10,5223979215
Click to expand...
Click to collapse
great. thanks. it worked. still cant believe it. But thank you very very very much.
t-rayms said:
great. thanks. it worked. still cant believe it. But thank you very very very much.
Click to expand...
Click to collapse
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time??
devil anand said:
Just hit thanks!!
I went to Android mtk website ...then I knew where was the problem.
Note : SuperSU zip is used to root a phone via custom recovery (twrp,philzz) ...but in marshmallow you can't root your phone just by installing SuperSU zip ....you need to install a custom *kernel* first ....remember next time
Click to expand...
Click to collapse
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
t-rayms said:
i take it that this step Then tap on wipe option and then factory reset and confirm it. fixed the bricking of the phone
and these steps After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
rooted the phone right?
One other thing is, whenever theres a system update, during the rebooting it does an error and i have to remove battery to restart the phone. Does rooting the phone cause updates not to work?
Click to expand...
Click to collapse
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...??
devil anand said:
You took a bit ....if you have rebooted your phone after just factory reset .....you may have got bootloop again.....(stuck on boot animation).
About your second problem ....
When the error happens in between these steps of installation .......you tap on reboot and install and your phone goes to recovery and after successful installation your reboots .
What's the error ??
Yeah rooting your phone changes system which causes problem while installation of the original update...
Click to expand...
Click to collapse
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
Just unroot your phone and try updating again !!!??
devil anand said:
First download a custom kernel zip (recommend thunderzap 5.1)
Then SuperSU 2.54 zip
Move this to files to your phones sd card
And again go to the menu which I told you during recovery (power and volume+ buttons at same time holding) then navigate to fastboot and enter ....you will se fastboot mode in the last line of the menu .
Now connect your phone to pc and open toolkit and press root.
You will see philz recovery loaded on your phone (philz recovery written on the top).
Then tap on wipe option and then factory reset and confirm it.
After factory resetting tap on install zip and select thunderzap zip
After successful installation of thunderzap select SuperSU zip and after installation of super su ...reboot now .......it will take 10 -15 mins......
Click to expand...
Click to collapse
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Johnny_16 said:
It worked for me too, but now I can`t update SuperSU.
Update from OS failed, from TWRP gives bootloop.
I`m on CM13 SNAPSHOT.
... also front camera cant take picture, but preview works ok.
Click to expand...
Click to collapse
What's the need of updating SuperSU ..,...
Use Google camera ....
Sent from my A1 using XDA-Developers mobile app
t-rayms said:
i get the prompt about an update ready for install, i click on it, it does the prompt to reboot so i choose to reboot. During the rebooting it tries to install updates, then the robot image comes up with the word "error". Stuck there until battery is removed. Afterwards the phone will turn back on.
Click to expand...
Click to collapse
You've root? And which update do you wanna install on your phone!?
Just tell me what's your build number.. I'll help ya out.
HELP
My cousins Myphone Uno is not turning on when pressing the power button, but if I put in a charge the screen turns on after a few minutes showing the battery but I don't know if it is charging. after a minute the display will go out and the screen flashes a once or twice then off and screen turns on and display the battery it will be on a loop, I can still get to boot option when screen flashes starts,
it shows:
[Recovery Mode]
[Fastboot Mode]
[Normal Boot]
[Normal Boot +ftrace]
[Normal slub debug off]
but when I select any options or not to ,the phone will turn off. Can you help me find a way to make this phone work again? thank you in advance!
PS: If I connect it in my PC it wasn't detected and the the loop will go on and on.
Usb debugging mode is also turned off