Related
So, firstly, big thanks to the devs here. Gt ADB up and running and started the seemingly easy process f flashing ClockworkMod.
However, I'm not getting to ClockworkMod after resetting. If I try booting into recovery, it stays on the birdie splash screen with "Recvery key detected" and "Booting recovery kernel image" in the upper left.
Not finding any options for alternate recoveries or a fix for this.
I bought it used and the original owner had done some stuff to it so perhaps I was not meant to flash Clockwork from here.
Tap UI version is TnT Lite v5.0.0
Kernel version is 2.6.32.9-00001-g0e0c333-dirty
The standard ClockworkMod does not work properly with TnTLite 5.0. You need the one that was specifically compiled for that ROM.
Go here: http://forum.xda-developers.com/showthread.php?t=998663
and scroll down to the bottom of the first post for a link to the compatible version.
I thought that might be the case although I was told I could flash CLockworkmod once 5.0 was on there.
I'm normally a bit better at figuring all this out but starting in the middle of someone else's work has me at an awkward spot.
I've been searching with little luck. Any chance of pointing me in the right direction?
What about a complete factory reset? Would it be advised at this point?
I editted my previous post with a link to TwoTapsX (Experimental) which is identical to TnTLite 5.0. That should get you going but I'm not sure how much damage might be done at this point. I would try just installing the compatible version of CWM and see if that works. If not, we can look at other recovery options.
Just in case... Are you familiar with nvflash? http://forum.xda-developers.com/showthread.php?t=861950
Just started reading about nvFlash and paused to ask the questions before hacking away blindly at my new toy.
I really appreciate you pointing me in the right direction.
I enjoyed the ROM he put on here but, like the poster under me, my data suddenly got deleted and I like to try various ROMs anyway so I set to work.
I rarely leave my tablet running the same ROM for more than 12 hours ;-)
Be aware that switching away from this particular one can be a bit tricky. I find that doing a cache and data wipe before starting helps to boost the success rate. I also try to down grade to stock 1.1-3588 before loading anything else. If that fails it usually results in nvflashing back to factory stock.
Ack! Okay, in what is sure to be yet another Windows 7 issue, I'm having trouble running the .bat file for nvflash.
Are you sure it is the Bat file. Windoz7 64 need a different driver for NVFLASH.
The drivers I used appeared to work. I will try again.
Damn, I'm sorry. I swear I'm usually better at figuring all this crap out for myself. Once I'm back to stock, I can work from the beginning. This is like being dropped into the middle of a David Lynch flick with zero context.
When I run the batch command, it says that nvflash.exe is not recognized as an internal or external command. Weird.
Did you extract both archives to the same directory?
I sure did. I did take it to mean the gtab folder should remain intact within the nvflash folder instead of mixing the contents altogether in one folder. Right?
Everything else seems to be in order.
Putting any recovery zip on the sdcard produces the same results. Thankfully, everything seems to be working aside from the recovery. Maddening!
I think they need to be intermixed. Would have to check the original thread or look at the .bat and .cfg files to be sure... but if I recall properly they do.
All the files from both zips should be in the same folder, otherwise the batch file can't find nvflash and you get that error.
Good luck!
Wow. If that's what it was they need to put a dunce cap on my avi. Thanks for all the help. I shoulda had the guy put it to stock so I could start from scratch.
I'll try that when I get home.
Thanks again!
Sent from my HTC Vision using XDA Premium App
Sleef,
You are in a world of hurt -- and I say that not making any negative comment
toward the advice you already have been given.
TnT Lite 5.0.0 (which is now TwoTapsx) is a second generation ROM Roebeet did
based on the UAT 3991 update posted by VS in a kind of test mode.
The second generation ROM is not compatible in many respects with the original ROMS
up to 3588 -- some of the internals that normally are changed in an update have been modified.
So, as you have been properly warned by others, you cannot run stock CWM. You
also have to be careful downgrading to stock before moving to stock or another ROM.
To get out of 5.0.0 you need to:
1. Read Roebeet's TwoTapsX thread so you know what you are working with:
http://forum.xda-developers.com/showthread.php?t=998663
2. You need to NVFlash back down to stock. Normally we'd tell you to follow
the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Since you already have been working with this, I'd step-by-step make
sure of your setup and that it is right.
My best suggestion would be for you to set up and follow the NVFlash thread above
exactly and see if you can get a good flash. If you do, it will take you down to what
we call bekit 1105, which is stock version 2638. If you get there and boot successfully,
then when you turn on wifi it will soon update you to OTA 3588. Then
you can carefully pretty much do what you want.
If you don't get a successful flash (because the tab has had so many different,
difficult to handle things on it), then all of us will have to help you find a successful
path.
Good luck,
Rev
P. S. -- What the other guys have been telling you is good -- I've just tried to
put it in perspective so you'd understand where you're at and be organized in
your approach.
Quick clarification... I think Rev meant to say "Is NOW TwoTapsX" rather than not which is why that thread is referenced later. The name change was necessary to differentiate the two development paths.
Thanks for popping in Rev. I've been meaning to pop in but I've been... practicing my recovery methods... don't ask...
Yep.
Fumblefingers strikes again. Thanks.
Rev
guys tried two roms including this one and it gives me "jumping to kernel (custom)..." freeze ...how to fix it up?
I have original rom installed, copied the Android folder /sdcard/Android
ran the Haret and thats the results as stated above ...
The model: HD2 (original 6.5 rom)
plz help
thanks!
Update your Radio
how do i make this radio update? my device is not rooted.
thanks!
Please search. There are a large amount of threads about that.
Hint: http://forum.xda-developers.com/showthread.php?t=808015
codiak said:
Please search. There are a large amount of threads about that.
Hint: http://forum.xda-developers.com/showthread.php?t=808015
Click to expand...
Click to collapse
Any one click apps to update radio on stock roms?
You have to understand what you are doing. Otherwise you can get in trouble.
So you have to read...
Oh, and this is the wrong forum by the way!
This is the right one for you question.
there is no shorten click and run guide for radio update? no way run android/haret without update the radio?
As I said: This is the wrong Subforum for you question!
Download official stock ROM 3.14 from the HTC website, it should be available for all carriers. This will give you a good enough radio.
Sorry to post if this is inapropriate thread but just thought id chip in with my experience of this issue...There are two solutions i have come across for being stuck at the "jumping to kernel" issue
1. Reeboot phone into WM...as soon as hd2 boots, go straight to the android folder and again boot to android using the haret method (main point to note is to do this as soon as WM boots..ie; do nothing else in wm. Just go straight to file xplorer then android...This works for me every time.
2. Put hd2 into 'Airplane Mode' (in WM) the try booting to android via the haret method.
This has worked for me in the past but not sure if is 100% failsafe However method 1 always works...for me anyway
Another thing to note is you should give it enough time for the build to create when you get to the green htc logo (after jumping to kernel) if this is your first install..In fact you may want to start fresh by a new re-formatt of sd card and fresh android install. Just incase anytjing has been messed up when you were stuck @ JTK as i assume you would have pulled the battery, which may have disturbed an image being built
This is dev section, not Q&A/General.
Which is the best rom to go with?
I've downloaded _n0p_'s DSC v0.7 and Tenorntex's Longhorn 2.1 v2, seeing as these 2 were the newest and latest and had Android 2.3.3
Are there any other better rom's or has anyone tried the 2 I listed, if so whats the difference?
Thanks
Better is very vague when it comes to ROM's it all depends on what you want in a Rom. I have old Simple Streak 1.2. Yes there is newer ROM's out but this one works perfect for what I need. In my Case Stability.
DSC is the most actively developed/supported. Plenty stable for me. I don't think any of the earlier Froyo based ROMs are being developed further.
I meant as far as Stability, Performance and up to date, I don't care about the Stage UI and was gunna theme it myself or use SPB Shell 3D.
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
n1nj4Lo said:
Could someone point me in the direction to an easy install rom?
I don't wanna install "these update pkg's" after renaming and then plug my phone into the pc and open cmd and then type this in on the pc. et cetera et cetera
I just wanna download a zip drag it to the card, bootup in safemode and install from sd card.
I'd consider doing all that work if I weren't testing out the device.
I won it off ebay, the guy replaced the screen and said it's been randomly rebooting ever since. But he never did a factory reset or new rom install ever since fixing the screen, so I just wanna simply install a rom and see if it works then go on from there.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
marvin02 said:
Unfortunately I do not believe that anyone can change the way that the Streak works just so it is more convenient for you or so that you don't have to learn anything.
In the time you took to navigate to XDA and make your post you could have flashed a ROM onto your Streak - plugging it in and everything.
The only ROM you can install by just putting it on the SD Card is the same one that is currently on the Streak, if you don't mind holding down a couple of buttons and using recovery mode.
Click to expand...
Click to collapse
So would that be this: Streak_407_20707_14.pkg ? According to the first post above me do I rename it?
Strephon Alkhalikoi said:
If anyone is wondering why developers leave and give the site a bad reputation look no further. Someone with over 600 posts under his username should not be making noob posts like this one. With so many posts he knows how to use the search engine and the wiki, but I guess when it comes to our device using the search engine and the wiki is an inconvenience, along with renaming a file "update.pkg".
Click to expand...
Click to collapse
Some people learn better through interaction where they can actually ask questions... I don't have over 600 posts so who are you talking about? Furthermore if you are talking about first thing I'd do is learn how to read mr wise guy, secondly!! You tell me how one is supposed to learn which rom is the best based on user reviews and opinions, where do I go to find that out and wheres the wiki on that, unless you expect people to read 200 and 300 page threads also? I have barely 150 posts and rarely post at all unless it is to ask questions or make requests. It's not like I have 600 posts and every single one of them are questions.
This is only my second time dealing with android and second time flashing android first time it was simply moving a zip to the sdcard and booting up into safe mode and selecting update through sdcard, so certainly I'd be baffled and have questions when one time it was so easy and the second time I've gotta jump through hoops and everything.
Lastly since WHEN Is asking a Question SOOOO wrong in the Dell Streak 5 Q&A Category???? It's not like I posted it in the wrong area or something, but ohhh no'es how dare n00b be confused and need a lil help/guidance of some experienced users, ohh mercy me the drama in that!!
Last time I checked that is what XDA is here for, for people to learn, not to be attacked by asshat trolls like you.
If anyone is wondering why XDA has a multitude more lurkers than posters look no further than to the hardass that is Strephon Alkhalikoi View Postwho can't stand to see a n00b in need of help!
Like this
Flashing/Updating
Installing a recovery
Download appropriate recovery to flash from Stock Recoveries or Custom recoveries
Enter fastboot mode on your phone
Flash recovery with fastboot: fastboot flash recovery <path to recovery.img>
After flashing is complete: fastboot reboot to reboot
Finished
If you are using a custom recovery see Disabling recovery overwrite in stock roms and follow the steps there to prevent the Streak from over writing the recovery. Re-install your custom recovery after following those steps.
Click to expand...
Click to collapse
BUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
n1nj4Lo said:
. . . .
Like thisBUT THE VERY FIRST THING THE WIKI SAYS IS To Stay AWAY From Fastboot, but this tells you to use Fastboot... So what gives and which is it? LoL
Click to expand...
Click to collapse
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
marvin02 said:
I hope that you can actually read better than that. The wiki does not say to stay away from fastboot. It clearly states two commands that should not be used on the Streak. It goes onto give a number of examples of using fastboot.
I hope that you other 157 posts (as I wtite this) on XDA were not as tiresome or ill-informed as the ones you have posted here.
The information you need is here in the forums, available at the links in my signature, and on other forums. Please exercise some patience and read the info.
Click to expand...
Click to collapse
Uhh yea sory... I forgot about the 2 options to stay away from, just the dangerous part stayed with me. LoL
Do I need to be at a certain android version or can I make a semi-major update leap?
Also it says
Installing a stock rom
Reinstalling a stock rom will wipe all data!
1. Download stock rom pkg and recovery to install
2. Copy pkg to sdcard and rename to update.pkg
3. Install matching stock recovery
4. Enter recovery mode
5. After recovery loads press Camera to begin process
6. Finished
Click to expand...
Click to collapse
Do I need the recovery.img as well? It said nothing about a img file or anything just said "matching stock recovery" so yea, is that the right thing?
_
First I'm gunna try factory reset and see if that fixes the random reboot problem, hopefully it does the seller said he just installed the new screen and never did anything except for just trying to powering it up, use normally and it would reboot suddenly.
WELL NO DUH, you need to restore everything back to default settings with a factory/hard reset. Thats like trying to install a video card or webcam and expecting it to work right away without installing the dirvers. - Hopefully!
Well it's only getting as far as the dell logo screen/splash screen. I've tried the entering safe mode but nothing yet, once it's powered on it just sits at that screen.
dsc is great and very stable if you dont mind the few following quirks.
1. google maps will always run in the background unless you freeze it. This will drain your battery quite quickly
2. Wifi might or might not be broken, if it is broken use wifi analyzer if not profit
the benefits of dsc?
fast
running GB instead of froyo
dpi change is awesome.
screen default orientation is awesome
stable other than those few bugs
Battery life was decent.
-------------
Im however just running 2.2 froyo on a stock rogers. The battery life is amazing on stock 2.2 (a whole day, and still have about 30% with heavy usage and constant 3g) and the wifi works fine. For me this is the most stable rom however it is a bit slow compared to DSC. This phone is used for work so it has to just.. work.
---------------
Havent really tried the other roms yet, but depending on what you want out of the phone you can try the DSC and see if you can live with these little quirks.
Yea I was leaning more towards DSC than Longhorn, it looks like it's updated more frequently too.
Bad & Good News
Turns out when the guy replaced the screen he fried the mobo... Me and a friend at a small local pc store tried everything from rooting with new rom to factory resets. Always had the same problem.
But the guy at the pc store sells phones also and said he'd give me $100.00 credit to a new factory refirbed, rooted and unlocked dell streak mini if I gave him the one we tried to repair.
I've been trying to understand all the steps necessary to replace the OEM ROM in my HTC Amaze 4G phone, but I can only find a disjointed set of pieces about the various steps and not one overarching document that covers all the stages of custom ROM flashing. A lot of the docs are aimed at the "insiders" of the Android developer community and few to people like me who would just like to try something better than what that ICS update did to my phone.
Having dabbled at one time with Linux from version .98 to 2.6 and being software developer most of my working life, I figure this should be easy for me. Yet, I find the documentation frustrating. I only imagine what it must be for others with less computer experience than me.
Since Android is based on Linux, I don't understand the big fuss about rooting. In Linux having the rooting privilege simply meant having a root password. Why is Android so much more complicated than that? Also, loading a new Linux kernel used to be a fairly simple process if one used compiled modules. The installation script pretty much took care of it. Android totally obscures this process and the disjointed documentation doesn't seem to help much. A lot of it assumes certain knowledge by the reader as if he/she was also an "insider" in that circle.
On my part I would like to so the following steps documented:
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
2.) How to prepare the phone for installing a new ROM
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
5.) How the flashing process would look like? Expected phases and length?
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
7.) Any special issues when booting the new ROM for the first time?
8.) How would I restore the original factory ROM saved in step 1?
Some of you might think I ask too much from guys who do the dev work as a hobby but I always thought that if one does something, might as well do it right, regardless of pay.
Well, that's my 2 cents worth for the day.
Howdy. I'll try to answer some of the questions you asked.
I would also recommend talking with @ravike14 who can easily guide you through the back up and routing and s-off process. It's not that difficult really. The most bizarre thing for me was sticking a piece of wire into a hole in the back of the phone to short out a process to achieve s-off.
With the right recovery image installed, it won't matter where you place the Rom.zip. which may be named just about anything. But it will always be a zip file.
The important one is the PH85img.zip must be placed in the root of your external sdcard. That file is loaded when you boot into the bootloader. And is for updating firmware.
Once you have root, and have made a nandroid backup, flashing is easy.
If you download viper, it is vipera1.7.2.1.zip. you can have it anywhere on you internal or external sdcard.
If you use 4ext recovery, you can select install and it will take you to a directory that you can browse to the place where the Rom, whatever name it is, is stored.
Click the Rom zip file and you will be guided thru the install process, if it has an aroma installer, or it will just install otherwise.
Then reboot and go thru the set up as if it was a brand new phone.
If you don't do the s-off thing, 4ext offers a smart flash option. If you aren't s-off you can't just flash a Rom if it contains a kernel. So smart flash will be required.
There are a few guides in the dev section and the general section on how most of this process works.
Again, talk with ravike and he'll be glad to help. Plus the more people we can keep here and happy, the longer we will be creating roms and fun stuff to play with.
Regards,
Chevy
Sent from my HTC_Amaze_4G using xda app-developers app
Is there a good documentation for all ROM flash steps?
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Your welcome!
NWsoccerfan said:
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Click to expand...
Click to collapse
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
chevycowboyusa said:
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
Click to expand...
Click to collapse
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
chevycowboyusa said:
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
Click to expand...
Click to collapse
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
chevycowboyusa said:
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
Click to expand...
Click to collapse
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
chevycowboyusa said:
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
Click to expand...
Click to collapse
Aroma? That doesn't smell too good to me.
chevycowboyusa said:
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
Click to expand...
Click to collapse
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
chevycowboyusa said:
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
Click to expand...
Click to collapse
I've got this.
chevycowboyusa said:
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
Click to expand...
Click to collapse
Thanks. I like your attitude about this.
When you get time stop by
XDA University.
I learned tons here its a great place to start and much better than trying to Google everything
http://forum.xda-developers.com/general/xda-university
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
been busy
NWsoccerfan said:
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
Aroma? That doesn't smell too good to me.
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
I've got this.
Thanks. I like your attitude about this.
Click to expand...
Click to collapse
you're welcome! I wish everyone would try to learn this
and the university is also very helpfull as freakboy noted above,
I've been busy working at bringing the comunity the next greatest romz!
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.