Related
Hi! first of all i dont know if this is the right forum to right this question. Dont know if it should be in the Dream forum but i have a magic, so i write it in the Magic forum.
My problem is that i for some reason can't flash Cyanogen's ROMs.
I have had Cyanogen's 4.0.3 ROM on my magic, but a couple of days ago i decided to upgrade it and try the Experimentel version 4.1.8.
I First tried to use the CM Updater, but for some reason it did not work, it would not flash the ROM.
So i downloaded the ROM manually and did as i always do: boot in recovery, wipe, apply and then reboot. Everything went fine until the reboot. After reboot the phone gets stuck at the HTC Magic screen, and nothing happens, only thing i can do is to remove the battery and the try and boot the phone again, and then it just get stuck at the HTC Magic screen again.
I have no problem flashing a MyHero 1.1.1. It works perfect.
I have also tried with a number of the other Cyanogen ROM versions, even tried 3.9.1 (cant remember the exact version number) have also tried the 4.0.3 version that did work before all this happened, but still no luck.
I have tried installing the Cyanogen Recovery image and the flash the Cyanogen ROM, but it still gets stuck at the HTC Magic screen.
I have tried reformating my sdcard and then flash, but no luck.
Can it be that i need a new SPL, Radio or something?
My current Fastboot screen looks like this:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
If anyone know what i need to do to get the Cyanogen ROM on my magic, i would really like to know.
Any suggestions would be much appreciated. Hope to here from you.
Per
Cyanogen is built for 32B (You seem to have a 32A) so you need to flash a 32A-kernel on top of the cyanogen ROM.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=544854
do what psyduck says, AND wipe before you do it. going from a stable to an experimental build requires a wipe or you will have a lot of issues.
Okay, thx for the answer both of you.
So i just "flash" the kernel first, like if it was an normal update? e.g. rename it update.zip, push it to sdcard, wipe, flash and then reboot. And then flash the ROM like i would normal do?
But what if I would like to flash a stable build, e.g. 4.0.4 what do i do then? i can't find a kernel for that in the link. Or can i just use 1 of the kernels in that link?
Per
Cyanogens ROM first! Otherwise the kernel will be overwritten with the one included in the cyanogen ROM.
Don't know why the old kernels were removed? Better to ask in the linked thread.
Decided to try Donut on my MT3G and had the same issue, I did a wipe after I noticed it didn't get past the first splash screen and that fixed it.
Thx for the help all of you, im now on the Cyanogen ROM, finally. its good to be back
But have 1 last question: When i deside to upgrade the current Cyanogen ROM im on now, i would also need to flash a new kernel right?
the thread listed by PsyDuck has it.
first page, look at the file called "Base Kernel v4.1.9.2"
link for it is right below.
Use amonRA's Recovery so you dont have to rename the updates.
download CM's latest 4.1.9.2 ROM and the basekernal. put both in root directory of SD.
boot into recovery, nandroid backup, wipe, Flash ROM then Flash update.
reboot. should work fine.
I did so, and everything works now. really nice, finally
32a looping after flashing CyanogenMod 4.1.99
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Thanks for replying. I didn't manage to flash successfully before that's why not able to do a nandroid backup ... unless of course if someone is willing to share the backup with me.
str4vag said:
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Click to expand...
Click to collapse
Same Boat
I have the same problem when flashing CM 4.1.99[9] ROMS. It goes into the endless boot/reboot mode.
I used to have the problem with the HoFo ROM as well (between versions 2.0.5 - 2.0.9). HoFo started working after that. I don't know what changed.
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
ranger79 said:
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
Click to expand...
Click to collapse
Hey guys, I just flashed and rooted my phone--primarily to install Arabic fonts in order to read Arabic text and websites. However, the characters are not appearing right to left as they should and the letters should be connected.
So I was reading and I was reading that installing the latest Cyanogen rom 4.2.15 and then applying an update will solve this problem. However, I cannot find out where to download this version of Cyanogen. I've tried to look for it, but I can't find it, can somebody please point me to the right direction? Does anybody know if even installing this does indeed solve this problem?
(I cannot post the link to the thread that is telling me to do it...the system won't allow it since I'm a new user)
Next time, post this in the Q&A section.
And, I just googled it, and this is what I found.
Not sure if this does what you're asking for, but it's worth a shot. To install this, I'm pretty sure you just flash CM 4.2.15, and then flash this on top of it.
I don't know if CM 4.2.15 will solve your problem, but here is where you can download it.
http://www.megaupload.com/?d=8UBN4VC1
That zip has a bunch of extra files you won't need. It's taken from this guide http://forums.t-mobile.com/t5/Operating-System-Software/GUIDE-New-very-easy-way-to-root-G1-even-if-it-has-1-6-android/td-p/237395. It does have what you're looking for, in cm421.zip.
Thank you both soooo much for the quick responses. I'm currently testing this out and will update with my situation...btw this should work for the Mytouch 3G as well right?
Shadowafs8 said:
Thank you both soooo much for the quick responses. I'm currently testing this out and will update with my situation...btw this should work for the Mytouch 3G as well right?
Click to expand...
Click to collapse
Yes, it will work for the MT3G, assuming that you have a 32B.
And you're welcome.
Wait...another quick question. Do I have to go through flash rec, or can I go straight to installing the zip?
Shadowafs8 said:
Wait...another quick question. Do I have to go through flash rec, or can I go straight to installing the zip?
Click to expand...
Click to collapse
Well, if you already used flash rec, then you have a recovery already installed on your phone. So if you have used that already, turn off your phone, and then press Home+Power to boot into recovery. You should be able to just flash the zip from there.
However, you might be using an outdated recovery. I would recommend switching to the newest Amon_RA recovery if you are on an outdated one. Instructions for installing that recovery are in his post in the MyTouch 3G Android Development section.
Alright, so I downloaded that .zip with the CM mod. I went to the home + power button menu and installed that zip. Once that was done, I installed that Arabic update zip u provided earlier and then rebooted. It's on the Mytouch 3G screen for about five minutes, is this normal?
EDIT: I wiped my factory settings and reinstalled the cm mod 4.2. It boots up fine. Do I have to rename that Arabic zip to update.zip then go to the update.zip option and update use that?
I downloaded it to see what the contents are. Yes, you'll want to flash it in the same way you flashed CM, which is from recovery. Be sure to do a nandroid backup in order to restore things later if it doesn't work out for you.
By the way, I'm not sure if that rom I gave you is 4.2.15 or 4.2.1. For future reference, you can find all the builds including 4.2.15 here: http://mirror.kanged.net/cm/stable/
If you want a better recovery I suggest either Amon Ra: http://forum.xda-developers.com/showthread.php?t=721792 or Clockwork: http://forum.xda-developers.com/showthread.php?t=639153
I personally use Amon Ra, however Clockwork has an app-based GUI, allowing you to flash updates like this one a little bit easier. I still use that CM 4.2.1 on a regular basis, occasionally flashing the new CM6 nightly builds. I find 4.2.1 to be very fast and stable, with Swap enabled and Zeam launcher.
Ahhh you gave me CM 4.2.1 which is why that Arabic rom didn't work properly lol...thanks for the mirror links, I'll download and install CM 4.2.15 right now and apply that Arabic update to see what comes of it...hopefully the end of my problems
Great news, it works perfectly now! The mirror link you gave me for CM 4.2.15 and the arabic rom is fully installed perfectly.
Though I have a question about Amon_RA recovery. I downloaded the .img file so with this, I'm I suppose to go into Flash Recovery and insert the path of the .img file then flash it that way? I think this is the way to go, but I'd like to confirm it just in case it's not and something happens
Shadowafs8 said:
Great news, it works perfectly now! The mirror link you gave me for CM 4.2.15 and the arabic rom is fully installed perfectly.
Though I have a question about Amon_RA recovery. I downloaded the .img file so with this, I'm I suppose to go into Flash Recovery and insert the path of the .img file then flash it that way? I think this is the way to go, but I'd like to confirm it just in case it's not and something happens
Click to expand...
Click to collapse
If you have CM 4.2.15, you should have an app called Terminal Emulator. Place the .img file on the root of your sdcard, and type this into Terminal Emulator.
Code:
su
flash_image recovery /sdcard/recoveryname.img
Obviously, replace "recoveryname.img" with the name of the recovery you are trying to use.
Press enter at the end of each line, and to see if it flashed, press home+power, and you should see your new recovery. If you ever have any problems with flashing a recovery, use fastboot. It's the safest way to flash recoveries, but it requires adb to be setup on your computer. I'm glad everything is working fine now.
Excellent, it worked out fine. The only problem was that I couldn't type numbers in my terminal (something that I thought would be fixed in this version of CM), but I renamed it to recovery.img and it worked out fine. I"m now updating Nandroid, BART, and Google just to be on the safe side of things.
Now I have to repeat this for the G1, which is a bit more complicated with the radio and SPL settings
Thanks a lot for everything guys, this is such a great community, I'm definitely sticking around on this forum
How to fix perfect SPL without Gold card. Include new 1.33.2013 SPL.
It’s possible to flash engineering SPLs, to replace your prefect SPL (1.33.2006, 1.33.2010, 1.33.2013, other) without Gold card. I did it on my 32B, sure method will work on 32A and other devices.
First short idea, then in steps.
First root your phone (soft root), then through Market download ROM Manager app, install Clockwork (or alternate Amon_RA) recovery, and immediately press boot into recovery. Phone will reboot into recovery, and now you can flash engineering SPL from SD card.
Now by steps
1. Download Engineering SPL from Amon_RA collection here. Put it (zip file) to your FAT32 formatted SD card. (1.33.2005 is common working)
2. Download newest version of SuperOneClick rooting program from here. Install program to your PC.
3. Connect phone, run program and use button Shell Root. This will soft root your phone. (Please read details instructions in program topic).
4. From phone, through Market, install 'ROM Manager' application. (Internet connection required).
5. Run app, press install Clockwork (or alternate Amon_RA) recovery. App will download latest recovery and install it. Immediately press boot to recovery.
6. Phone will boot into recovery, choose 'flash zip from SD' and choose your previously downloaded Engineering SPL.
7. After flash will ask to reboot, and choose reboot from menu.
8. After reboot phone will finish flashing SPL, and DONE!
NOW U can reboot into recovery yourself, by pressing 'HOME' + 'POWER' keys (from switched off phone). From recovery U can flash Radio, ROMS, do backup, etc.
If U would flash ROM, recommend to try Cyanogen MOD ROM first. There are detailed instructions for flashing on Cyanogen WIKI page.
If on step 6 phone not boot into Recovery, but showing splash screen with '!' sigh. Reboot phone and back to step 3 and go through steps again, but on step 5 flash OTHER recovery then used previously (Clockwork OR Amon_ra). Please keep in mind, (1) that Soft Root working until reboot, and (2) that You have to reboot into recovery immediately after flashing it. Other ways U have to start again, from step 3.
Would mention, that most ROMs not working with newest radio, and You have to flash old radio to ROMs start loading on your device.
Thanks to CLShortFuse, Amon_RA and all other developers.
After spending one day for SPL hack and flashing 12 different ROMs I've ended with recovering original latest Google ROM FR83D. Because no other could compare to fast and stable of original unrooted rom.
AMAZING!
This worked for me with the 2010 SPL for my MyTouch 3G 1.2. I don't know how or why, but this is amazing. I've bricked my phone from trying to change the SPL, and this worked perfectly. I think there is a simpler method to this though.
I got full root using Universal Androot, then flashed the stock +Rooted MyTouch 3G 1.2 ROM. If you do this, then you can start from step 6.
THIS IS AMAZING. THANK YOU VERY MUCH!
when i flash the recovery and boot into it just goes to the green mytouch splash screen and does nothing.. if i try to boot into recovery manually with power and home it goes to the black screen with the exclamation triangle and a phone...
Thanks, it works with me.
Regards.
franky_402 said:
when i flash the recovery and boot into it just goes to the green mytouch splash screen and does nothing.. if i try to boot into recovery manually with power and home it goes to the black screen with the exclamation triangle and a phone...
Click to expand...
Click to collapse
If on step 6 phone not boot into Recovery, but showing splash screen with '!' sigh. Reboot phone and back to step 3 and go through steps again, but on step 5 flash OTHER recovery then used previously (Clockwork OR Amon_ra). Please keep in mind, (1) that Soft Root working until reboot, and (2) that You have to reboot into recovery immediately after flashing it. Other ways U have to start again, from step 3.
So I tried flashing a new SPL following this method. I got softroot and installed Amon Ra's recovery via ROM Manager. I then booted into recovery and flashed Engineering SPL 1.33.2010 (seemed like the newest version) now my phone is stuck in a boot loop.
I can get into recovery but the phone will not boot into the OS or anything.
Prior to this, my HBOOT was 1.33.0013 (the one that came with the official 2.2.1 update from T-Mobile)
Any thoughts on how I could fix this? This isn't my primary phone since I have a G2 but I would like to get my old MyTouch3G to work.
----UPDATE----
I got into fastboot (forgot that I needed to hold the back button) and I see that HBOOT is now 1.33.2010 and I have S-OFF. Is there some incompatibility with my radio (shows 2.22.29.25) and this HBOOT?
After SPL flash U have to flash ROM and some times radio too. New ROMs will not work with older SPLs and new radios some time not work with some ROMs. So, flash new ROM from Recovery.
I would recommend to flash Cyanogen MOD ROM for first try. There are detailed instructions for flashing on Cyanogen WIKI page? dont flash SPL, because U already did, start from step ROM flash.
Good luck
smapdi said:
So I tried flashing a new SPL following this method. I got softroot and installed Amon Ra's recovery via ROM Manager. I then booted into recovery and flashed Engineering SPL 1.33.2010 (seemed like the newest version) now my phone is stuck in a boot loop.
I can get into recovery but the phone will not boot into the OS or anything.
Prior to this, my HBOOT was 1.33.0013 (the one that came with the official 2.2.1 update from T-Mobile)
Any thoughts on how I could fix this? This isn't my primary phone since I have a G2 but I would like to get my old MyTouch3G to work.
----UPDATE----
I got into fastboot (forgot that I needed to hold the back button) and I see that HBOOT is now 1.33.2010 and I have S-OFF. Is there some incompatibility with my radio (shows 2.22.29.25) and this HBOOT?
Click to expand...
Click to collapse
thanks liberatemail, it works on my magic
I am trying to help my friend to flash his magic 32a which with original HTC sense android 1.5. I did root it but coouldn't install Rom manager 3.0.1.3. Which version do I need, I found or on market but it's not free like I install on my ginger yoshi magic, why?
Sent from my HTC Magic/Dream using XDA App
ROM manager avaible from Market.
To install original ROM try to look recovery flashing in top topics
ginoyang said:
I am trying to help my friend to flash his magic 32a which with original HTC sense android 1.5. I did root it but coouldn't install Rom manager 3.0.1.3. Which version do I need, I found or on market but it's not free like I install on my ginger yoshi magic, why?
Click to expand...
Click to collapse
Error occurred while attempting to run priveledged commands
Rogers HTC Magic
pvt 32a
spl: 1.76.0010 (50000)
radio: 6.35.16.19
build:3.54.631.4
I run soft root on superoneclick and it says I'm rooted. Installed Rom Manager. Attempted to 'Flash ClockworkMod' and got the following message: 'An Error occurred while attempting to run priveledged commands'. Re-ran Superoneclick and it says device is already rooted. Any ideas?
liberatemail said:
After spending one day for SPL hack and flashing 12 different ROMs I've ended with recovering original latest Google ROM FR83D. Because no other could compare to fast and stable of original unrooted rom.
Click to expand...
Click to collapse
Where can you get that FR83D ROM? Thanks!
darkguy2008 said:
Where can you get that FR83D ROM? Thanks!
Click to expand...
Click to collapse
Please look in treads names some where here
http://forum.xda-developers.com/forumdisplay.php?f=493
facevalue said:
Rogers HTC Magic
pvt 32a
spl: 1.76.0010 (50000)
radio: 6.35.16.19
build:3.54.631.4
I run soft root on superoneclick and it says I'm rooted. Installed Rom Manager. Attempted to 'Flash ClockworkMod' and got the following message: 'An Error occurred while attempting to run priveledged commands'. Re-ran Superoneclick and it says device is already rooted. Any ideas?
Click to expand...
Click to collapse
try to install alternate recovery manager from Rom Manager
liberatemail said:
Please look in treads names some where here
http://forum.xda-developers.com/forumdisplay.php?f=493
Click to expand...
Click to collapse
Well that was helpful...
... NOT.
I mean, duh, I know how to search, and it's not in the first page, so it must be a really old ROM or it doesn't has FR83D in the name.
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please